docs(btdb): register BTDB Manager in the Overview docker registry; record the local rig

- ZB.MOM.WW.Overview appsettings.Docker.json: application "BTDB Manager", instance manager at
  http://zb-btdb-manager:9877 (HasActiveRole false); docker/README.md fleet row.
- CLAUDE.md BTDB row and sister-project-history/btdb.md §7/§9: docker/ layout, the
  dacpac + SQL CLR side-project build, scadabridge-mssql as the BT host.

Claude-Session: https://claude.ai/code/session_015dYqtaTxgf6NK2KuwriMSg
This commit is contained in:
Joseph Doherty
2026-09-04 06:14:22 -04:00
parent 370a9eea96
commit 54f111e8b1
4 changed files with 35 additions and 3 deletions
+4 -1
View File
@@ -25,11 +25,14 @@ The dev rigs publish only some node ports to the host:
| OtOpcUa central-1/2 | container `:9000` | **no** — only Traefik `:9200`, load-balanced across the pair |
| OtOpcUa site-\* (4) | container `:8080` | **no** — not published |
| HistorianGateway | container `:5220` | yes — `localhost:5220` |
| BTDB Manager | container `:9877` | yes — `localhost:9877` |
| MxAccessGateway | windev `:5130` | yes, with the VPN up |
So a host-run dashboard can only see part of the fleet. This stack joins the three rig networks
(`otopcua-dev_default`, `scadabridge-net`, `zb-historiangw_default`, all declared `external`) and
addresses every node by container DNS name, which is how it sees all of them.
addresses every node by container DNS name, which is how it sees all of them. BTDB Manager
(`~/Desktop/BTDB/docker`) sits on `scadabridge-net` too, because its BT database lives on
ScadaBridge's infra MSSQL container, so no fourth network is needed for it.
Ports above were established by probing the running rigs on 2026-07-24, **not** read off the
compose files — the two disagree. In particular OtOpcUa's site nodes serve health on `:8080`, not
@@ -25,6 +25,8 @@
// LocalDb sync re-bind the primary HTTP port)
// ScadaBridge central :5000
// ScadaBridge site :8084 (MetricsPort; MapZbHealth lands here from the site-health work)
// BTDB Manager :9877 (BTDB/docker; single instance, joins scadabridge-net for BT;
// /health/ready is 503 whenever that database is unreachable)
//
// ManagementUrl values stay host-relative (localhost:*) on purpose: they are followed by the
// OPERATOR'S BROWSER, not by this container, so container DNS names would be dead links.
@@ -146,6 +148,18 @@
}
]
},
{
"Name": "BTDB Manager",
"ManagementLabel": "Manager",
"Instances": [
{
"Name": "manager",
"BaseUrl": "http://zb-btdb-manager:9877",
"ManagementUrl": "http://localhost:9877/",
"HasActiveRole": false
}
]
},
{
"Name": "MxAccessGateway",
"ManagementLabel": "Dashboard",