Arguments
Publish
Section titled “Publish”To deploy an app instead of starting the server, use mercury publish.
See Publish from the terminal for sign-in, file selection,
and deployment options.
Log level
Section titled “Log level”Would you like to see more logs from mercury?
Please use --log-level=INFO or --log-level=DEBUG. The default log level is CRITICAL.
Session sharing
Section titled “Session sharing”Use --keep-session to give all viewers of an app one shared Python session.
Widget changes and resulting outputs are synchronized across connected browsers.
Mercury runs one notebook rerun at a time; changes received while it is busy are
coalesced into the next rerun, starting at the earliest affected cell.
Without this option, each viewer gets independent widget values and kernel state.
Timeout
Section titled “Timeout”Would you like to limit your server resources with usage timeout?
Please set --timeout=600. The timeout value is in seconds.
Working directory
Section titled “Working directory”By default, Mercury uses the current directory as the base for notebooks and related files.
To override it, use --working-dir=/path/to/notebooks.
When provided, Mercury will use that directory as the base for:
- notebook discovery,
- relative notebook paths passed on startup,
config.tomllookup,- relative file reads from inside notebooks.