Give the work queue its own Redis root, and pin what the suite runs as
The queue shared the `pipeline:` prefix with flow state, so `RedisState.clear()` could DEL the queue stream and `keys()` enumerated queue entries — only callers filtering `__`-prefixed names kept it safe. It moves to `queue:` without a migration: whatever is in flight at the upgrade is dropped once, documented in DEPLOY.md rather than papered over. Alongside it: `pool_pre_ping`, so a connection idle across a Postgres restart costs a round trip instead of a failed request; the test suite pins ENVIRONMENT=local and DOMAIN=localhost itself rather than inheriting a deployment's .env; and `depth` leaves the queue stats, where it reported the capped journal length as if it were a backlog. ALERTS_FILE and PANELS_FILE now point at /data. They defaulted to a path on no volume, so alert routing and every wall-panel pairing were living in the container's writable layer and vanishing on each rebuild. Carrying the existing files across is a manual step; DEPLOY.md has it. development.md was still the upstream template — compose.override.yml, localhost.tiangolo.com, `docker compose watch` as the dev flow — and said nothing about the Playwright suite. Rewritten against what the Makefiles actually do. deployment.md was template text too, duplicating the root DEPLOY.md, and is gone. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Uq8mtNb97A7praJLyeEYgs
This commit is contained in:
@@ -154,6 +154,11 @@ services:
|
||||
# credential and the key it pinned, so losing it on a rebuild would mean
|
||||
# enrolling again by hand. Absent until someone connects a portal.
|
||||
- CLOUD_CONFIG_FILE=/data/cloud.json
|
||||
# Alert routing and the wall-panel pairings. Both are written at runtime,
|
||||
# so off the volume they would land in the container's writable layer and
|
||||
# be lost on the next rebuild — un-pairing every screen.
|
||||
- ALERTS_FILE=/data/alerts.json
|
||||
- PANELS_FILE=/data/panels.json
|
||||
|
||||
volumes:
|
||||
- app-flow-data:/data
|
||||
|
||||
Reference in New Issue
Block a user