e393a7a111
All checks were successful
PR build (required check) / changes (pull_request) Successful in 6s
secrets-guard / encrypted (pull_request) Successful in 5s
PR build (required check) / build-backend (pull_request) Has been skipped
shell-lint / shellcheck (pull_request) Successful in 6s
PR build (required check) / build-frontend (pull_request) Has been skipped
PR build (required check) / validate-observability (pull_request) Has been skipped
PR build (required check) / gate (pull_request) Successful in 1s
sync-dev rendered deploy/secrets/dev.yaml into /etc/thermograph.env unconditionally. That path is dev's env file — and it is also BETA's, on the box beta is still running on until the cutover completes. With the dev checkout present, the next push to dev would have overwritten the live env file of the environment currently serving beta.thermograph.org: its containers would keep running (env_file is read at container start) and then come up on the next deploy pointed at dev's database password. The earlier run only escaped this by failing first on the missing checkout. Gate the render on the host's own secrets-env marker, which provision-dev.sh flips to 'dev' only after beta has vacated. Until then the job syncs the checkout and skips the render loudly rather than failing, so the ordering is enforced by the host's own statement of what it is rather than by remembering to do the steps in the right order. |
||
|---|---|---|
| .. | ||
| backup | ||
| db | ||
| forgejo | ||
| migrations | ||
| openmeteo | ||
| secrets | ||
| stack | ||
| swarm | ||
| twa | ||
| Caddyfile.vps1 | ||
| Caddyfile.vps2 | ||
| deploy-dev.sh | ||
| deploy.sh | ||
| env-topology.sh | ||
| migrate-db.py | ||
| POSTGRES-MIGRATION.md | ||
| provision-agent-access.sh | ||
| provision-dev.sh | ||
| provision-mail-supervision.sh | ||
| provision-mail.sh | ||
| provision-secrets.sh | ||
| render-secrets.sh | ||
| RUNBOOK-vps1-vps2-cutover.md | ||
| thermograph-dev.service | ||
| thermograph.env.example | ||
| thermograph.service | ||