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

chore(docker): env2 runs its own image tag, leader-auto-down overlay, drill targets env2 (#116)

Browse Source 
- docker/build.sh: SCADABRIDGE_IMAGE picks the tag (default scadabridge:latest).
- docker-env2/docker-compose.yml: node image is ${SCADABRIDGE_IMAGE:-scadabridge:latest},
  so env2 can run its own build without retagging the primary rig's image.
- docker-env2/docker-compose.leader-auto-down.yml: opt-in overlay for both env2 pairs,
  mirroring docker/docker-compose.leader-auto-down.yml. Shipped default stays auto-down.
- docker/failover-drill.sh: DRILL_ENV=primary|env2 (container prefix, Traefik :9100,
  pair site-x).

Claude-Session: https://claude.ai/code/session_01GT67ACmpMR7b9LGRPLijMi
This commit is contained in:
Joseph Doherty
2026-11-12 23:09:59 -05:00
parent a92a418d7f
commit e8a743de9f
5 changed files with 69 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docker-env2/deploy.sh
+3 -1
View File
@@ -13,7 +13,9 @@ fi
echo "=== ScadaBridge Env2 Docker Deploy ==="
# Reuse the primary build (same scadabridge:latest image, same network creation)
# Reuse the primary build (same scadabridge:latest image, same network creation).
# SCADABRIDGE_IMAGE=<repo:tag> builds and runs env2 on its own tag instead (build.sh and
# the compose file both read it), leaving scadabridge:latest untouched.
"$SCRIPT_DIR/../docker/build.sh"
# Ensure env2 databases exist on the shared scadabridge-mssql