corgi why
corgi why
Explain in one call why a service is not up
Synopsis
Runs the diagnosis by hand nobody wants to repeat: unmet dependencies, who owns the port, the last exit code, missing or unresolved env, and the tail of the service's own log.
Reports a single machine-readable verdict — healthy, crashed, not_started, dependency_unready, port_taken, env_missing, no_start_command or unhealthy — so a script or an agent can branch without reading prose.
corgi why <service> [flags]
Examples
corgi why api
corgi why api --json
Options
-h, --help help for why
--log-lines int How many trailing log lines to include (default 8)
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