blissful-infra status
status shows what exists and whether it is running. What it prints depends on your use context.
blissful-infra statusblissful-infra status [name]| Argument | Effect |
|---|---|
| (omitted) | Scoped to your current context |
<name> | Show that tenant, one-shot. Your context is not changed |
What it shows
Section titled “What it shows”| With no context set | With a tenant set | With tenant/project set |
|---|---|---|
| All tenants and whether they are up | That tenant’s projects, services and port block | That project’s services with live health |
Live health means the CLI actually probes each service, so a container that is running but failing its health check shows as unhealthy rather than up.
Examples
Section titled “Examples”blissful-infra status # whatever your context coversblissful-infra status acme # one-shot look at another tenantBecause [name] does not change your context, you can check on another tenant mid-task without having to use your way back.
Finding your ports
Section titled “Finding your ports”Ports are allocated deterministically per tenant and project index, so they are predictable but not memorable. status is the fastest way to see what a given tenant actually got: Grafana, Jenkins, Kafka, Postgres, the gateway and each service’s HTTP port.