Expand description
What the daemon keeps beside a compose stack’s definition: its
environment (.env text that ${VAR} resolves against), its managed
domains (domain records per service, merged in at deploy), and a record
of each deploy (Deployment), kept per stack under
stack-meta/<stack>/ in the stack’s org directory.
A record is written when a deploy is handed to the controller
(deploying) and finished by a watcher thread that follows the rollout:
done when every service converged, failed when one fails or pauses
or the rollout outlasts its timeout, superseded when a newer deploy
came first. It keeps the compose source it deployed, the environment
and managed domains of the moment (secret references, never values),
the stack’s events while it ran, and the output of each service’s last
replica that failed to come up during it.
Structs§
- Deployment
- One deploy of a compose stack.
- LogLine
- One line of a deployment’s log: an event of its stack.
- Stack
Meta - The per-stack settings and records, for every org.
Enums§
Constants§
- KEEP_
DEPLOYMENTS - Deployment records kept per stack, as for an app.