znetsixe 5d95f8bfcc feat(cloud): harden nginx-proxy + sql foundation; HTTP-01 interim cert plan
Wire up the three foundation stacks (nginx-proxy, sql, portainer) in
cloud/compose.yml and add real configs for the first two.

nginx-proxy
- Base nginx.conf with http + stream contexts, modern TLS profile,
  client_max_body_size baseline for gitea LFS / mlflow artifacts.
- Vhosts under conf.d/: grafana, gitea, keycloak, nodered, mlflow,
  jupyter, portainer (HTTPS upstream), rabbitmq, jenkins. WebSocket
  upgrade headers where needed (grafana live, node-red editor,
  jupyterhub kernels, jenkins agents).
- conf.d/00-default.conf serves /.well-known/acme-challenge/ on :80
  and 301-redirects everything else.
- stream.d/mqtt.conf terminates MQTT-TLS at 8883, proxies to
  rabbitmq:1883 internally.
- All vhosts reference /etc/letsencrypt/live/infra/* — a stable path
  via certbot --cert-name infra, so the wildcard migration changes
  nothing in the vhost files.
- README documents: HTTP-01 SAN interim during Versio period →
  DNS-01 wildcard via certbot-dns-transip after migration; bootstrap
  procedure (self-signed fallback → real cert issuance → reload).

sql
- config/init.d/01-databases.sh provisions gitea/keycloak/mlflow
  databases + roles on first start. Idempotent only via fresh
  data volume — change the script after first run requires
  manual psql or a volume wipe.
- compose env extended with GITEA_DB_PASSWORD, KEYCLOAK_DB_PASSWORD,
  MLFLOW_DB_PASSWORD.

cloud
- include: now wires nginx-proxy + sql + portainer. Other stacks
  stay commented for future rounds.
- .env.example adds KEYCLOAK_DB_PASSWORD and sensible defaults
  (LETSENCRYPT_EMAIL, GRAFANA_ROOT_URL, KEYCLOAK_HOSTNAME,
  GITEA_ROOT_URL, POSTFIX_FROM_DOMAIN all pointing at wbd-rd.nl).
- Operator note inline: bring portainer's standalone instance down
  before deploying via cloud compose; comment its ports: block.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-21 13:43:35 +02:00

infra

R&D infrastructure stacks for Waterschap Brabantse Delta. Hub-and-spoke deployment: one cloud central hub + per-plant edge sites.

Layout

infra/
├── stacks/         # reusable, runnable stack defs (kebab-case)
├── cloud/          # the single central hub
├── sites/          # per-plant edge deployments
└── docs/           # architecture + conventions

Stacks are pulled into the cloud and site composes via the Compose Spec include: directive. Each stack is also runnable standalone for testing.

Quick start

# Cloud hub (run on the central server)
cd cloud
cp .env.example .env       # fill in real secrets
docker compose up -d

# A plant edge (run on the edge gateway at the plant)
cd sites/<plant>
cp .env.example .env
docker compose up -d

Stacks

Stack Purpose Cloud Edge
node-red Flow-based automation
influxdb Time-series database
grafana Dashboards / SCADA
keycloak Identity / SSO
portainer Container management UI
nginx-proxy Stock nginx + certbot sidecar
rabbitmq General-purpose broker (AMQP + MQTT plugin)
postfix Outbound mail relay
wireguard-server VPN server
wireguard-client VPN client
gitea Git server (HTTPS-only)
jenkins CI/CD
sql Config DB (postgres 16)
mlflow ML experiment tracking + registry
jupyterhub Multi-user notebook server
mosquitto MQTT broker for FROST stack only

Sites

Site Status
gemaal1 Scaffolded — awaiting hardware provisioning

Design

See docs/architecture.md for the hub-and-spoke topology, 4-network model, ingress table, and the reasoning behind each choice.

Conventions

  • kebab-case folder names
  • compose.yml (Compose Spec), not docker-compose.yml
  • Stack composes pulled into cloud/site via include:
  • Secrets in .env files (gitignored); .env.example committed with placeholders
  • OT layer (OPCUA, PLCs) is out of scope for this repo
Description
No description provided
Readme 171 KiB
Languages
Shell 56.5%
JavaScript 26.8%
Python 13.4%
Dockerfile 3.3%