livebook-dev/livebook
1
1
Fork 0
mirror of https://github.com/livebook-dev/livebook.git synced 2025-10-06 11:35:54 +08:00
Code Issues Projects Releases Packages Wiki Activity

Mention Docker deployment

Browse source
This commit is contained in:
José Valim 2023-10-17 15:04:31 +02:00
parent 797844223a
commit e9e760c7da
1 changed files with 4 additions and 19 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
lib/livebook/notebook/learn/deploy_apps.livemd
View file

@ -255,25 +255,10 @@ locally, you may be wondering: can I actually ship this production?
The answer is yes!
You can do so in any platform that supports Docker containers.
For example, imagine you have a folder called "public-apps" with
all of your public notebooks you want to deploy. You can then
run your own Livebook image which points to said directory:
```dockerfile
FROM ghcr.io/livebook-dev/livebook:latest
COPY /path/to/my/public-apps /apps
ENV LIVEBOOK_APPS_PATH "/apps"
ENV LIVEBOOK_APPS_PATH_WARMUP "manual"
RUN /app/bin/warmup_apps.sh
```
You may also set additional environment variables, [see the complete
list](https://github.com/livebook-dev/livebook#environment-variables).
Some of them, such as `LIVEBOOK_PASSWORD`, must be set directly on
your deployment platform, with the value of your choice, if you want
to access and debug your deployed notebooks in production.
Click on the <i class="ri-livebook-deploy"></i> icon on the sidebar
and you will find a "Deploy with Docker" link. Clicking on the link
will open up a modal with instructions on deploying a single notebook
or a folder with several entries through Docker.
If you want to develop and deploy notebooks as a team, check out
[Livebook Teams](https://livebook.dev/teams).