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

Docs

Browse source
This commit is contained in:
José Valim 2023-08-10 10:16:56 +02:00
parent 74ca662bf3
commit 543c3eb002
1 changed files with 12 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -280,7 +280,7 @@ If you want to develop and deploy notebooks as a team, check out
## Where to go next ## Where to go next
There are many types of applications one can build with There are many types of applications you can build with
notebooks. For example, we can use the foundation we learned notebooks. For example, we can use the foundation we learned
here to develop any type of form-driven application. here to develop any type of form-driven application.
The structure is always the same: The structure is always the same:
@ -295,14 +295,17 @@ to all users. With the `to: origin` option, the changes are
visible only to a given user. This means you get full control visible only to a given user. This means you get full control
if the application is collaborative or not. if the application is collaborative or not.
Livebook also supports multi-session applications, where each [Livebook also supports multi-session applications](https://www.youtube.com/watch?v=dSjryA1iFng),
user gets their own Livebook session (each running under their where each user starts their own Livebook session on demand.
own Elixir runtime). Furthermore, instead of starting the By using `Kino.Input` and `Kino.interrupt/2`, it is common to
application upfront, multi-session applications are started on build multi-session applications that execute step-by-step,
demand. These differences mean multi-session apps may rely on similar to regular notebooks, without a need to setup form
different techniques during development and have their own controls and events handlers as done in this guide.
trade-offs during deployment. To learn more, here are some Furthermore, each session in a multi-session app has their
resources to dig deeper into them: own Elixir runtime, which provides isolation but also leads
to higher memory usage per session.
To learn more about apps, here are some resources to dig deeper:
* [The announcement of Livebook apps with livecoding of * [The announcement of Livebook apps with livecoding of
the application built in this guide](https://www.youtube.com/watch?v=q7T6ue7cw1Q) the application built in this guide](https://www.youtube.com/watch?v=q7T6ue7cw1Q)