How are we going to ship livebook?

[josevalim]

I am thinking we can start by using escripts but we should also consider shipping a release or using bakeware in the future.

Escripts are the most convenient for Elixir developers, so we should definitely consider it. The only downside of escripts is that it can't serve assets from the "priv" directory, so we will have to embed them like we did in the live dashboard.

[josevalim]

Oh, one of the things about the livebook escript is that we should likely support multiple modes. For example, we will add livebook server but also livebook render path/to/notebook.lmd --as [markdown | html] [--elixir | --mix | --remote NODE].

[wojtekmach]

I think escript is a fantastic start. For much broader adoption at a later date Id consider using https://github.com/bake-bake-bake/bakeware.

[josevalim]

When we do this, we should probably unify def/prod config, especially because there shouldn't be many differences between them, except maybe for code reloading in dev?

The other question is how we are going to configure the escript and the view app and if we can unify it somehow. We should probably support both environment variables and command line stuff for escripts, while releases/mix supports only env vars.