CLI Overview

mdocker is a single bash entry point that dispatches every verb. This section documents each verb group in full; start here for the conventions that apply everywhere.

mdocker up my-project
# port pre-flight ok · attached to edge · TLS ready
# → https://my-project.coding9.test

Command shape

Most commands follow the pattern:

mdocker [--json] <verb> [<subverb>] [<project>] [args…] [flags…]

Some verbs are grouped (config, profile, terminal, git, share, shop, db, service, host, edge) and take a subverb, e.g. mdocker config set ….

Global flags

Flag	Meaning
`--json`	Emit machine-readable JSON instead of formatted text. Supported by read-only verbs. Can be placed before the verb, e.g. `mdocker --json git info aurora`.

Exit codes

Code	Meaning
`0`	Success.
`1`	Generic error (an internal `die`).
`2`	Port-conflict pre-flight failed — no free replacement port was found.

See Exit Codes & JSON Output for scripting details.

Conventions

Read-only vs. mutating. Diagnostic verbs (ls, inspect, health, stats, doctor, config show/get, git info, edge status/logs) never change state.
Registry-driven. Verbs that act on a project take its name (from the registry), not its path. Register a path once with init.
Overrides, never edits. Mutating verbs rewrite generated files under ~/.config/multi-docker/; your original compose files are never touched.

Verb groups

MultiDocker · Coding9 GmbH