From e9e760c7da749d0979c9e623b4e8059340ac94e3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jos=C3=A9=20Valim?= Date: Tue, 17 Oct 2023 15:04:31 +0200 Subject: [PATCH] Mention Docker deployment --- .../notebook/learn/deploy_apps.livemd | 23 ++++--------------- 1 file changed, 4 insertions(+), 19 deletions(-) diff --git a/lib/livebook/notebook/learn/deploy_apps.livemd b/lib/livebook/notebook/learn/deploy_apps.livemd index 8a497eb23..4b6d6ce7d 100644 --- a/lib/livebook/notebook/learn/deploy_apps.livemd +++ b/lib/livebook/notebook/learn/deploy_apps.livemd @@ -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 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).