monoceros stop

Pauses the workbench - the workspace container and any services it declares. Containers go to Exited; data, volumes and the network are preserved, so a monoceros start brings the same state back. It removes nothing and frees essentially no disk - for that, use monoceros remove. With an <app> argument it instead stops a long-running server inside the workbench.

monoceros stop <name> [--service <svc>]        # pause the workbench
monoceros stop <name> <app> [--target <t>]     # stop an app inside it

The form is chosen by argument count: no <app> is container lifecycle, an <app> addresses a long-running app server.

Stop an app inside the workbench

monoceros stop <name> <app> [--target <t>]

Stops a long-running server started from the app’s launch config. It signals the whole process group (so children like node under npm or java under Maven stop too), then cleans up the process-state file. <app> is a path under projects/; --target defaults to the app’s default target (or its only one). Stopping the workbench itself does not require stopping apps first.

Inside the container

The build agent (which has no host monoceros) stops the same app with the in-container runner:

monoceros-ctl stop <app> [--target <t>]

The host command above is just a docker exec onto exactly this - one mechanism, two entry points. See Long-running app servers.

Examples

monoceros stop acme                          # pause the whole workbench
monoceros stop acme --service postgres       # pause just one service
monoceros stop acme web                       # stop the "web" app's default target
monoceros stop acme apps/api --target dev     # stop a specific target

Options

--service <svc> - stop only one service (e.g. postgres) instead of the whole workbench. Only meaningful when the yml declares services.
--target <t> - with an <app>, which launch target to stop. Defaults to the app’s default target, or its only one.

Behavior

Preserves everything. Data, volumes and the network survive untouched.
Tears down the shared proxy when no other workbench still needs it, so it is not left running for nothing.
Frees almost no disk. To reclaim space, use monoceros remove.
App stop kills the process group and removes its .monoceros/run/ state file; the workbench keeps running.