ShipDay two
Operate apps and releases
Read the live state, redeploy safely, stop or start service, and use the one retained rollback target.
Use Overview as the source of truth
The app header identifies the selected application, current state, managed URL, privacy mode, CPU, memory, and deployment count. Overview separates control-plane status from exact local runtime evidence.
Running means the active container is healthy locally. Live means the matching public route is also active. Stopped means service is intentionally offline without deleting configuration or releases.
Choose the right lifecycle action
| Action | Use it when |
|---|---|
| Stop | You want to stop traffic and compute while retaining releases and configuration. |
| Start | A stopped app has a valid successful release and should return online. |
| Redeploy | The saved source changed and you want a new immutable release. |
| Rollback | The latest successful deployment is unhealthy and the immediately previous release is available. |
| Delete | You intentionally want to remove this app after reviewing database and route impact. |
Read deployment history
Deployment history marks the release that is Live now and, when valid, the one Rollback available target. Older releases are read-only history.
Rollback performs health checks and route activation before retiring the newer release. If route acknowledgement is ambiguous, LiveHQ reconciles exact signed status instead of guessing.
Use logs and metrics
- Logs show bounded recent stdout and stderr for the exact active provider instance.
- Metrics report current CPU, memory, network, block I/O, and process count.
- A warming metric or log panel is not automatically an application failure; verify health and the public URL.
- Use Advanced diagnostics only when normal status and recovery guidance are insufficient.
Change resource limits deliberately
Memory and CPU changes create controlled runtime work. Choose limits that fit the Mac while leaving room for Docker Desktop, databases, sibling apps, and macOS.
LiveHQ does not autoscale local compute. The capacity is the capacity of the Mac you operate.