zmeel run is the single command to get a Zmeel instance running. It runs onboard (if no config exists), then doctor, and finally starts the server. Once the server is healthy, it opens the dashboard in your browser.
Usage
run starts the onboarding wizard automatically. If the terminal is non-interactive and no config exists, the command exits with an error and directs you to run zmeel onboard first.
Options
Local instance ID to use. Defaults to
default. Use this to run multiple isolated instances side by side (for example --instance dev and --instance staging).Attempt automatic repairs when
doctor finds fixable issues. Enabled by default.Disable automatic repairs during the doctor check. Issues are reported but not fixed.
Path to the config file. Defaults to
~/.zmeel/instances/default/config.json.Data directory root. Isolates all state from
~/.zmeel.Examples
What happens when you run it
- Resolves the instance — sets the instance ID from
--instanceor theZMEEL_INSTANCE_IDenvironment variable (default:default). - Checks for a config file — if none exists and the terminal is interactive, starts
zmeel onboard. - Runs doctor — checks configuration, database connectivity, storage, secrets, and port availability. Repairs fixable issues automatically (unless
--no-repairis set). If any checks fail, the server does not start. - Starts the server — the Zmeel server and web UI become available at
http://localhost:3100(or the port set in your config). - Generates a bootstrap invite (if needed) — if your deployment mode is
authenticatedand you are using embedded PostgreSQL,rungenerates a one-time admin invite URL after the server starts.
Server URL
The server starts athttp://localhost:3100 by default. The port and host are set during zmeel onboard or with zmeel configure --section server.