Server/socket mode

Mimamoru can run in server/socket mode with --enable-socket. In this mode a unix socket is created to which you can attach via mimamoru attach (note that the origin/root dir must be the same, by default thats your CWD).

To prevent logs from being output two times (on the server stdout and attached process) you can also specify --quiet on the server.

Attach command

Examples:

# Attach to all output from a watch group
mimamoru attach backend:

# Attach to a specific daemon/prep step
mimamoru attach backend:server

# Attach to daemon/prep step from any watch
mimamoru attach :server

# Attach to everything
mimamoru attach

This will stream logs from the server, looking like this:

[backend:mimamoru|out] File watcher and process manager for development workflows
[backend:mimamoru|out]
[backend:mimamoru|out] Usage:
[backend:mimamoru|out]   mimamoru [flags]
[backend:mimamoru|out]   mimamoru [command]
...
[backend:test|out] ?    gitlab.com/TECHNOFAB/mimamoru/cmd/mimamoru      [no test files]
[backend:test|out] ?    gitlab.com/TECHNOFAB/mimamoru/internal/cmd      [no test files]
...

To remove the prefix [backend:test|out] for example use --raw-logs when attaching.