mix do local.rebar --force, local.hex --force   # 首次使用 Mix 时初始化 rebar/hex（官方原文）
mix escript.install hex livebook                # 安装最新稳定版（本环境实测锁定 0.19.10）

==> phoenix_live_dashboard
Compiling 36 files (.ex)
Generated phoenix_live_dashboard app
==> livebook
Compiling 313 files (.ex)
Generated livebook app
Generated escript livebook with MIX_ENV=prod
Are you sure you want to install "livebook"? [Yn]

warning: you must append "/home/livebook/.mix/escripts" to your PATH if you want to invoke escripts by name

export PATH=$PATH:/home/livebook/.mix/escripts    # 安装器提示的 escripts 目录
ls -la /home/livebook/.mix/escripts              # 验证产物

total 12252
drwxr-xr-x 2 root root     4096 Oct 31 04:03 .
drwxrwxrwx 3 root root     4096 Oct 31 04:03 ..
-r-xr-xr-x 1 root root 12535245 Oct 31 04:03 livebook

livebook --help

Livebook is an interactive notebook system for Elixir

Usage: livebook [command] [options]

Available commands:

  livebook server    Starts the Livebook web application
  livebook deploy    Deploys a notebook to Livebook Teams

The --help and --version options can be given instead of a command for usage and versioning information.

livebook --version

Erlang/OTP 28 [erts-16.1.1] [source] [64-bit] [smp:128:6] [ds:128:6:10] [async-threads:1] [jit:ns]

Elixir 1.19.3 (compiled with Erlang/OTP 28)

Livebook 0.19.10

livebook badcmd; echo "exit=$?"

Unknown command badcmd
Usage: livebook [command] [options]

Available commands:

  livebook server    Starts the Livebook web application
  livebook deploy    Deploys a notebook to Livebook Teams

The --help and --version options can be given instead of a command for usage and versioning information.
exit=1

Usage: livebook server [options] [open-command]

An optional open-command can be given as argument. It will open
up a browser window according these rules:

  * If the open-command is "@home", the browser window will point
    to the home page

  * If the open-command is "@new", the browser window will point
    to a new notebook

  * If the open-command is a URL, the notebook at the given URL
    will be imported

  * If the open-command is a directory, the browser window will point
    to the open page with the directory selected

  * If the open-command is a notebook file, the browser window will point
    to the opened notebook

The open-command runs after the server is started. If a server is
already running, the browser window will point to the server
currently running.

## Available options

  --cookie             Sets a cookie for the app distributed node
  --ip                 The ip address to start the web application on, defaults to 127.0.0.1
                       Must be a valid IPv4 or IPv6 address
  --name               Sets a name for the app distributed node
  -p, --port           The port to start the web application on, defaults to 8080

The --help option can be given to print this notice.

## Environment variables

The following environment variables can be used to configure Livebook on boot:

  * `LIVEBOOK_ALLOW_URI_SCHEMES` - sets additional allowed hyperlink schemes to the
    Markdown content. Livebook sanitizes links in Markdown, allowing only a few
    standard schemes by default (such as http and https). Set it to a comma-separated
    list of schemes.

  * `LIVEBOOK_APP_SERVICE_NAME` - sets the application name used by the cloud
    provider to aid debugging.

  * `LIVEBOOK_APP_SERVICE_URL` - sets the application url to manage this
    Livebook instance within the cloud provider platform.

  * `LIVEBOOK_APPS_BANNER` - sets the value to render at the top apps banner.

  * `LIVEBOOK_APPS_PATH` - the directory with app notebooks. When set, the apps
    are deployed on Livebook startup with the persisted settings. Password-protected
    notebooks will receive a random password, unless `LIVEBOOK_APPS_PATH_PASSWORD`
    is set. When deploying using Livebook's Docker image, consider using
    `LIVEBOOK_APPS_PATH_WARMUP`.

  * `LIVEBOOK_APPS_PATH_PASSWORD` - the password to use for all protected apps
    deployed from `LIVEBOOK_APPS_PATH`.

  * `LIVEBOOK_APPS_PATH_WARMUP` - sets the warmup mode for apps deployed from
    `LIVEBOOK_APPS_PATH`. Must be either "auto" (apps are warmed up on Livebook
    startup, right before app deployment) or "manual" (apps are warmed up when
    building the Docker image; to do so add "RUN /app/bin/warmup_apps" to
    your image). Defaults to "auto".

  * `LIVEBOOK_AWS_CREDENTIALS` - enable Livebook to read AWS Credentials from
    environment variables, AWS Credentials, EC2/ECS metadata when configuring
    S3 buckets.

  * `LIVEBOOK_BASE_URL_PATH` - sets the base url path the web application is
    served on. Useful when deploying behind a reverse proxy.

  * `LIVEBOOK_PUBLIC_BASE_URL_PATH` - sets the base url path the `/public/*` routes
    are served on. Note that this takes precedence over `LIVEBOOK_BASE_URL_PATH`,
    if both are set. Setting this may be useful to create exceptions when deploying
    behind a reverse proxy that requires authentication.

  * `LIVEBOOK_CACERTFILE` - path to a local file containing CA certificates.
    Those certificates are used during for server authentication when Livebook
    accesses files from external sources.

  * `LIVEBOOK_CLUSTER` - configures clustering strategy when running multiple
    instances of Livebook using either the Docker image or an Elixir release.
    See the "Clustering" docs for more information:
    https://hexdocs.pm/livebook/clustering.html

  * `LIVEBOOK_COOKIE` - sets the cookie for running Livebook in a cluster.
    Defaults to a random string that is generated on boot.

  * `LIVEBOOK_DATA_PATH` - the directory to store Livebook's internal
    configuration. Defaults to "livebook" under the default user data
    directory.

  * `LIVEBOOK_DEFAULT_RUNTIME` - sets the runtime type that is used by default
    when none is started explicitly for the given notebook. Must be either
    "standalone" (Standalone), "attached:NODE:COOKIE" (Attached node)
    or "embedded" (Embedded). Defaults to "standalone".

  * `LIVEBOOK_FORCE_SSL_HOST` - sets a host to redirect to if the request is not over HTTPS.
    Note it does not apply when accessing Livebook via localhost. Defaults to nil.

  * `LIVEBOOK_HOME` - sets the home path for the Livebook instance. This is the
    default path used on file selection screens and others. Defaults to the
    user's operating system home.

  * `LIVEBOOK_IDENTITY_PROVIDER` - controls whether Zero Trust Authentication
    must be used for this Livebook instance. This is useful when deploying
    Livebook inside a cloud platform, such as Cloudflare and Google.
    Supported values are:

      * `basic_auth:<username>:<password>`
      * `cloudflare:<your-team-name (domain)>`
      * `google_iap:<your-audience (aud)>`
      * `tailscale:<tailscale-cli-socket-path>`
      * `custom:YourElixirModule`

    See our authentication docs for more information: https://hexdocs.pm/livebook/authentication.html

  * `LIVEBOOK_IFRAME_PORT` - sets the port that Livebook serves iframes at.
    This is relevant only when running Livebook without TLS. Defaults to 8081.

  * `LIVEBOOK_IFRAME_URL` - sets the URL that Livebook loads iframes from.
    By default iframes are loaded from local `LIVEBOOK_IFRAME_PORT` when accessing
    Livebook over http:// and from https://livebookusercontent.com when accessing over https://.

  * `LIVEBOOK_IMAGE_REGISTRY_URL` - sets the container image registry used to fetch livebook images from.
    By default uses `ghcr.io/livebook-dev/livebook`.

  * `LIVEBOOK_IP` - sets the ip address to start the web application on.
    Must be a valid IPv4 or IPv6 address.

  * `LIVEBOOK_LOG_LEVEL` - sets the logger level, allowing for more verbose
    logging, either of: error, warning, notice, info, debug. Defaults to warning.

  * `LIVEBOOK_LOG_METADATA` - a comma-separated list of metadata keys that should
    be included in the log messages. Livebook-specific keys include:
    - `users` (attached to evaluation and request logs)
    - `session_mode` (attached to evaluation logs, either "default" or "app")
    - `code` (attached to evaluation logs, the code being evaluated)
    - `event` (attached to evaluation logs, currently always "code.evaluate")

    By default includes only `request_id`.

  * `LIVEBOOK_LOG_FORMAT` - sets the log output format, either "text" (default)
    for human-readable logs or "json" for structured JSON.

  * `LIVEBOOK_NODE` - sets the node name for running Livebook in a cluster.
    Note that Livebook always runs using long names distribution, so the
    node host name must use a fully qualified domain name (FQDN) or an IP
    address.

  * `LIVEBOOK_PASSWORD` - sets a password that must be used to access Livebook.
    Must be at least 12 characters. Defaults to token authentication.

  * `LIVEBOOK_PROXY_HEADERS` - a comma-separated list of headers that are set by
    proxies. For example, `x-forwarded-for,x-forwarded-proto`. Configuring those
    may be required when running Livebook behind reverse proxies.

  * `LIVEBOOK_PORT` - sets the port Livebook runs on. If you want to run multiple
    instances on the same domain with the same credentials but on different ports,
    you also need to set `LIVEBOOK_SECRET_KEY_BASE`. Defaults to 8080. If set to 0,
    a random port will be picked.

  * `LIVEBOOK_SECRET_KEY_BASE` - sets a secret key that is used to sign and encrypt
    the session and other payloads used by Livebook. Must be at least 64 characters
    long and it can be generated by commands such as: `openssl rand -base64 48`.
    Defaults to a random secret on every boot.

  * `LIVEBOOK_SHUTDOWN_ENABLED` - controls if a shutdown button should be shown
    in the homepage. Set it to "true" to enable it.

  * `LIVEBOOK_TOKEN_ENABLED` - controls whether token authentication is enabled.
    Enabled by default unless `LIVEBOOK_PASSWORD` is set. Set it to "false" to
    disable it.

  * `LIVEBOOK_UPDATE_INSTRUCTIONS_URL` - sets the URL to direct the user to for
    updating Livebook when a new version becomes available.

  * `LIVEBOOK_WITHIN_IFRAME` - controls if the application is running inside an
    iframe. Set it to "true" to enable it. If you do enable it, then the application
    must run with HTTPS.

The environment variables `ERL_AFLAGS` and `ERL_ZFLAGS` can also be set to configure
Livebook and the notebook runtimes. `ELIXIR_ERL_OPTIONS` are also available to customize
Livebook, but it is not forwarded to runtimes.

## Examples

Starts a server:

    livebook server

Starts a server and opens up a browser at a new notebook:

    livebook server @new

Starts a server and imports the notebook at the given URL:

    livebook server https://example.com/my-notebook.livemd

mkdir -p /tmp/lbtest && cd /tmp/lbtest
env -u LIVEBOOK_PASSWORD \
    LIVEBOOK_HOME=/tmp/lbtest LIVEBOOK_DATA_PATH=/tmp/lbtest LIVEBOOK_IFRAME_PORT=4041 \
    livebook server --ip 127.0.0.1 --port 4040 > /tmp/lbtest/server.log 2>&1 &
sleep 12 && cat /tmp/lbtest/server.log

[info] Reading storage from /tmp/lbtest/livebook_config.v1.ets
[info] Running LivebookWeb.IframeEndpoint with Bandit 1.11.1 at 127.0.0.1:4041 (http)
[info] Running LivebookWeb.Endpoint with Bandit 1.11.1 at 127.0.0.1:4040 (http)
[Livebook] Application running at http://localhost:4040/?token=ii7sbfm5jdoybkamssfgpuur7xtvbbnd

elixir -e '{:ok, {{_, status, _}, _, body}} =
  :httpc.request(:get, {~c"http://127.0.0.1:4040/", []}, [], [])
IO.puts("HTTP #{status}  body_head=" <> String.slice(to_string(body), 0, 17))'

HTTP 200  body_head=<!DOCTYPE html>

livebook server --port 4040

Livebook already running on http://localhost:4040

[notice] SIGTERM received - shutting down

livebook deploy --help

Usage: livebook deploy [options] filename [filename...]

## Available options

  --org-token             Token from your Livebook Teams organization
  --teams-key             Teams key from your Teams workspace
  --deployment-group-id   The ID of the deployment group you want to deploy to
  --dry-run               Perform a sanity check but do not actually deploy

The --help option can be given to print this notice.

## Examples

Deploys a single notebook:

    livebook deploy --org-token="lb_ot_..." --teams-key="lb_tk_..." --deployment-group-id=123 path/to/app1.livemd

Deploys multiple notebooks:

    livebook deploy --org-token="lb_ot_..." --teams-key="lb_tk_..." --deployment-group-id=123 path/to/*.livemd

$RELEASE_ROOT/bin/livebook --help

Usage: livebook COMMAND [ARGS]

The known commands are:

    start          Starts the system
    start_iex      Starts the system with IEx attached
    daemon         Starts the system as a daemon
    daemon_iex     Starts the system as a daemon with IEx attached
    eval "EXPR"    Executes the given expression on a new, non-booted system
    rpc "EXPR"     Executes the given expression remotely on the running system
    remote         Connects to the running system via a remote shell
    restart        Restarts the running system via a remote command
    stop           Stops the running system via a remote command
    pid            Prints the operating system PID of the running system via a remote command
    version        Prints the release name and version to be booted

ERROR: Unknown command --help

$RELEASE_ROOT/bin/livebook version

livebook 0.19.10

$RELEASE_ROOT/bin/livebook eval "IO.puts \"eval_ok_\" <> to_string(6 * 7)"

eval_ok_42

$RELEASE_ROOT/bin/livebook rpc "IO.puts Node.self() |> to_string()"

livebook@127.0.0.1

$RELEASE_ROOT/bin/livebook pid; echo "exit=$?"

--rpc-eval : Cannot run --rpc-eval if the node is not alive (set --name or --sname)
exit=1

if [ "$RELEASE_COMMAND" = "rpc" ] || [ "$RELEASE_COMMAND" = "remote" ]; then
  export RELEASE_DISTRIBUTION="name"
  if [ ! -z "${LIVEBOOK_NODE}" ]; then export RELEASE_NODE=${LIVEBOOK_NODE}; fi
  if [ ! -z "${LIVEBOOK_COOKIE}" ]; then export RELEASE_COOKIE=${LIVEBOOK_COOKIE}; fi
else
  export RELEASE_DISTRIBUTION="none"
  export RELEASE_COOKIE="${RELEASE_COOKIE:-$(head -c 512 /dev/urandom | ... )}"
fi

1 error found!
--daemon : Unknown option

[error] Running LivebookWeb.IframeEndpoint with Bandit 1.11.1 at http failed, port 8081 already in use

ERROR!!! [Livebook] shutdown: failed to start child: {Bandit, #Reference<0.1436210281.3234070532.23998>}
    ** (EXIT) shutdown: failed to start child: :listener
        ** (EXIT) :eaddrinuse