trails-cool/trails
1
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update local-dev-stack proposal: staging now exists

Browse source 
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Ullrich Schäfer 2026-05-17 20:41:03 +02:00
parent 9d4c7d2b41
commit 0e77ac7831
No known key found for this signature in database
GPG key ID: A32FF691A0F752D9
1 changed files with 7 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

14
openspec/changes/local-dev-stack/proposal.md
View file

@ -1,12 +1,12 @@
## Why
There is no staging environment — production is the only deployed instance. Infra
changes (Prometheus alerts, Caddy config, Grafana dashboards) go straight to prod
with no way to validate them locally first. Meanwhile, CI E2E tests skip ~15 of
20 tests because there is no PostgreSQL service in the workflow, and BRouter was
only recently added to CI with manual setup instead of reusing the dev compose
file. The existing `docker-compose.dev.yml` covers PostgreSQL and BRouter but
nothing else from the production stack.
Infra changes (Prometheus alerts, Caddy config, Grafana dashboards) can only be
validated against staging or production — there is no way to test them locally
first. Meanwhile, CI E2E tests skip ~15 of 20 tests because there is no
PostgreSQL service in the workflow, and BRouter was only recently added to CI
with manual setup instead of reusing the dev compose file. The existing
`docker-compose.dev.yml` covers PostgreSQL and BRouter but nothing else from the
production stack.
## What Changes