corgi events
corgi events
Service lifecycle as a stream, instead of polling status
Synopsis
Reports what the stack is doing: a service starting, going ready, crashing or being stopped. Without --follow it prints the current state once and exits.
With --follow it stays open and emits a line per transition, so a script or an agent reacts to a crash instead of polling corgi status on a timer.
corgi events [flags]
Examples
corgi events --json
corgi events --follow --json --timeout 10m
Options
--follow Stay open and print each transition as it happens
-h, --help help for events
--interval duration How often to re-read the run state while following (default 1s)
--timeout duration Stop following after this long (0 = until Ctrl-C)
Options inherited from parent commands
--describe Describe contents of corgi-compose file
--dockerContext string Specify docker context to use, can be default,orbctl,colima (default "default")
-l, --exampleList List examples to choose from. Click on any example to download it
-f, --filename string Custom filepath for for corgi-compose
--fromScratch Clean corgi_services folder before running
-t, --fromTemplate string Create corgi service from template url
--fromTemplateName string Create corgi service from template name and url
-g, --global Use global path to one of the services
--interactive Force interactive prompts even when no TTY/agent detected
--isolate string Run this workspace under a named lease: own port block, own database names, own containers
--json Emit machine-readable JSON output
--privateToken string Private token for private repositories to download files
-o, --runOnce Run corgi once and exit
--silent Hide all welcome messages
SEE ALSO
- corgi - Corgi cli magic friend