dohertj2/ScadaBridge
1
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects Releases Wiki Activity

docs(drill): leader-auto-down env2 rollout - all #116 gates pass on central and site-x; env2 stays on it as the soak (#116)

Browse Source 
Claude-Session: https://claude.ai/code/session_01GT67ACmpMR7b9LGRPLijMi
This commit is contained in:
Joseph Doherty
2026-11-12 23:28:34 -05:00
parent e8a743de9f
commit cafdc0ce60
20 changed files with 513 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docker-env2/README.md
+21
View File
@@ -108,6 +108,27 @@ Both UIs are now reachable:
- Primary: http://localhost:9000
- Env2: http://localhost:9100
### Own image tag, and the `leader-auto-down` soak (ScadaBridge#116)
`SCADABRIDGE_IMAGE=<repo:tag>` makes `docker/build.sh` tag that image and this compose file
run it, so an env2 build never retags the `scadabridge:latest` the primary rig runs. Unset
keeps the old shared-image behaviour.
Since 2026-11-12 env2 is the soak environment for the `leader-auto-down` rollout and runs
`scadabridge:env2-116` with the opt-in overlay
[`docker-compose.leader-auto-down.yml`](docker-compose.leader-auto-down.yml). Keep both
when recreating nodes, and switch both pairs together:
```bash
SCADABRIDGE_IMAGE=scadabridge:env2-116 docker compose \
-f docker-env2/docker-compose.yml -f docker-env2/docker-compose.leader-auto-down.yml \
up -d --force-recreate --no-deps central-a central-b site-x-a site-x-b
```
Plain `deploy.sh` goes back to `scadabridge:latest` on the default `auto-down`. Drill:
`DRILL_ENV=env2 DRILL_PAIR=central|site-x bash docker/failover-drill.sh`. Record:
[`docs/plans/2026-11-12-leader-auto-down-env2-drill.md`](../docs/plans/2026-11-12-leader-auto-down-env2-drill.md).
### Teardown
```bash