docs: render architecture & flow diagrams as draw.io charts

Replace ASCII-art diagrams across the README and docs/ with editable .drawio sources plus exported PNGs, so the diagrams render clearly in rendered markdown and can be maintained/regenerated instead of being hand-edited as fragile text art. Non-diagram blocks (code, folder trees, UI wireframes) were left as text.
2026-05-31 23:32:53 -04:00
parent 3763f6d2d8
commit bdee12f4e9
71 changed files with 2461 additions and 516 deletions
@@ -17,29 +17,8 @@ A sibling `docker-env2/` directory with `deploy.sh` / `teardown.sh` / `seed-site

 ## Architecture Overview

-```
-                          (host machine)
-
-  Primary stack (already existing — unchanged)        Env2 stack (new)
-  ┌────────────────────────────────────┐              ┌──────────────────────────────┐
-  │ Traefik :9000  ◄── 9001/9002 UI    │              │ Traefik :9100 ◄── 9101/9102 UI│
-  │ Central A/B    (9011/9012 Akka)    │              │ Central A/B  (9111/9112 Akka) │
-  │ Site-A/B/C (9021..9044)            │              │ Site-X       (9121/9122 Akka, │
-  └─────────────┬──────────────────────┘              │              9123/9124 gRPC)  │
-                │                                     └──────────┬───────────────────┘
-                │                                                │
-                ▼  scadabridge-net (shared bridge network)  ◄──────┘
-        ┌──────────────────────────────────────────────────────────────┐
-        │ scadabridge-mssql        ScadaBridgeConfig      (primary DB)     │
-        │                        ScadaBridgeMachineData (primary DB)     │
-        │                        ScadaBridgeConfig2     (env2 DB) ← new  │
-        │                        ScadaBridgeMachineData2(env2 DB) ← new  │
-        │ scadabridge-ldap         (shared — same test users)            │
-        │ scadabridge-smtp         (shared Mailpit)                      │
-        │ scadabridge-opcua        (shared)                              │
-        │ scadabridge-restapi      (shared)                              │
-        └──────────────────────────────────────────────────────────────┘
-```
+![env2-architecture-overview](diagrams/env2-architecture-overview.png)
+<!-- source: diagrams/env2-architecture-overview.drawio — edit, then re-export with export-drawio.sh -->

 Both stacks attach to the same `scadabridge-net` Docker bridge so env2's app containers can reach the infra services by container hostname (`scadabridge-mssql`, `scadabridge-ldap`, etc.). Akka clusters are independent — each side's `SeedNodes` lists only its own central nodes, so they never gossip-merge despite sharing the network.