7e28e72c29
cd-apps already scp's `infrastructure/Caddyfile` to the server alongside docker-compose.yml — but the running Caddy container doesn't auto-pick-up config changes. cd-infra is the workflow that calls `caddy reload`, and it only triggers on `infrastructure/` paths. So any Caddyfile edit shipped through cd-apps (e.g. the `lb_try_duration` block in PR #329, deployed as part of an apps push) sits on disk unapplied until the next cd-infra run. This was real today: PR #329 added `lb_try_duration 30s` to silence deploy-time 502s. PR #331 (a vite.config edit, apps path) merged right after and triggered cd-apps, which copied the new Caddyfile but didn't reload Caddy. The very next planner restart in that deploy promptly produced three 502s — the exact thing #329 was supposed to prevent. We applied the reload manually via SSH after the fact. This commit makes that reload happen on every cd-apps deploy. The operation is idempotent (Caddy validates first, swaps live, no downtime) so doing it even when Caddyfile is unchanged costs nothing. `|| true` keeps the deploy from failing if Caddy is unhealthy at deploy time. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| workflows | ||
| copilot-instructions.md | ||
| dependabot.yml | ||