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

chore(docker): windev MxGateway API key no longer in the seed scripts

Browse Source 
docker/seed-sites.sh and docker-env2/seed-sites.sh hard-coded the windev
gateway API key. They now read MXGW_APIKEY from the environment, or from
a private file (default ~/.config/scadabridge/windev-mxgw-apikey,
override MXGW_APIKEY_FILE). With no key the MxGateway connection step is
skipped and the rest of the seed runs. READMEs note where to put it.

The key remains in git history (2 commits), so it should be rotated on
the windev gateway.

Claude-Session: https://claude.ai/code/session_01GT67ACmpMR7b9LGRPLijMi
This commit is contained in:
Joseph Doherty
2026-11-13 00:00:03 -05:00
parent 644f564c30
commit c3c1f6e870
4 changed files with 33 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docker-env2/README.md
+4
View File
@@ -83,6 +83,10 @@ bash docker-env2/seed-sites.sh
bash docker-env2/seed-data-path.sh
```
> The MxGateway data connections need the windev gateway API key, which is not in the repo. Put it in
> `~/.config/scadabridge/windev-mxgw-apikey` (mode 600), point `MXGW_APIKEY_FILE` at another file, or export
> `MXGW_APIKEY`. Without a key the script skips the MxGateway connection step and seeds everything else.
Site-x's LocalDb is **replicated** (node-a dials node-b on 8083, same dev key on both),
like the rig's site-a. Without it a site failover brings up an active node with no
deployed instances, connections or S&F buffer.