monoceros logs

Tails the named workbench’s logs: a Compose service, or a long-running app you started inside the container. Follows by default.

monoceros logs <name> [<app>] [--target <t>] [--no-follow]

With no second argument it follows all Compose services. The second argument is either an app (a path under projects/ that has a launch config) or a Compose service name (e.g. postgres):

an app tails logs/<app>/<target>.log, with --target selecting the configuration (defaults to the app’s default, or its only one);
anything else is treated as a Compose service.

Inside the container

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

monoceros-ctl logs <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 logs acme                       # follow all services
monoceros logs acme postgres              # just one Compose service
monoceros logs acme web                   # the "web" app's default target
monoceros logs acme web --target worker   # a specific target
monoceros logs acme --no-follow           # one-shot dump, then exit

Options

--target <t> - when the second argument is an app, which launch target’s log to tail. Defaults to the app’s default target, or its only one.
--no-follow - print what is there and exit instead of streaming. Following is the default (the explicit alias is -f).

Behavior

Follows by default, like tail -f; Ctrl+C stops following.
Read-only. It streams logs and changes nothing.