Fix Planner/Journal healthchecks; auto-clean compose orphans
The compose healthcheck for both apps was `curl -sf http://localhost:.../health`, but node:25-slim (Debian trixie-slim) ships neither curl nor wget, so the check always reported the containers as `unhealthy` even while they were happily serving 200s. Install curl in both Dockerfiles. Separately, today's flagship BRouter cleanup (PR #297) left an orphan `brouter` container behind because cd-infra's `docker compose up -d <list>` doesn't pass `--remove-orphans`. I had to remove it by hand. Pass the flag in both cd-infra and cd-apps so future service deletions clean up on the next deploy. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
c0b42e4743
commit
2e5606458d
4 changed files with 14 additions and 5 deletions
4
.github/workflows/cd-apps.yml
vendored
4
.github/workflows/cd-apps.yml
vendored
|
|
@ -105,7 +105,9 @@ jobs:
|
|||
# Pull and deploy app containers
|
||||
docker compose --env-file app.env pull journal planner
|
||||
docker compose --env-file app.env run --rm journal npx drizzle-kit push --config /app/packages/db/drizzle.config.ts --force
|
||||
docker compose --env-file app.env up -d journal planner
|
||||
# --remove-orphans cleans up containers whose service was deleted
|
||||
# from the compose file, matching cd-infra's behaviour.
|
||||
docker compose --env-file app.env up -d --remove-orphans journal planner
|
||||
|
||||
# Clean up
|
||||
docker image prune -af
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue