RnD/infra

Files

znetsixe 2f5e3b4183 feat: SQL=postgres, nginx+certbot, MQTT split, ML stacks, gitea HTTPS-only, gemaal1 site

Round-2 changes locking in scaffold-phase decisions and adding ML/notebook stacks.

Locked decisions
- sql: postgres 16-alpine (was TBD); init.d/ mount for per-app DB provisioning
- nginx-proxy: stock nginx + certbot sidecar (was nginx:alpine TODO).
  Chose stock over nginxproxy/nginx-proxy because stream{} is required for
  MQTT-TLS reverse-proxy on tcp/8883 to rabbitmq:1883.
- gitea: HTTPS-only (DISABLE_SSH=true). No SSH port published.

MQTT split
- Remove stacks/mqtt placeholder.
- Add stacks/rabbitmq — general-purpose broker (AMQP + MQTT plugin),
  used at both cloud and edge. External MQTT clients reach cloud broker
  via nginx stream-proxy on 8883.
- Add stacks/mosquitto — reserved for the FROST (SensorThings) stack
  only. Cloud-only. Internal to its own stack; no external ingress.

ML / notebooks (cloud-only)
- stacks/mlflow — experiment tracking + model registry. Postgres backend
  on sql stack; local volume for artifacts (S3/MinIO is a TODO).
- stacks/jupyterhub — multi-user notebook server. DockerSpawner via
  mounted docker.sock; users spawn into cloud-app network so they can
  reach mlflow, influxdb (via grafana), rabbitmq.

Sites
- sites/gemaal1 — first edge deployment scaffold. Site-local override
  template for binding nginx to PLANT_LAN_IP.

Docs
- README + docs/architecture.md updated: stacks table now lists 15 stacks,
  ingress + attachment tables reflect mlflow/jupyterhub, TLS strategy
  section locked, MQTT-split section added, Gitea HTTPS-only noted.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-21 13:22:46 +02:00

gemaal1

feat: SQL=postgres, nginx+certbot, MQTT split, ML stacks, gitea HTTPS-only, gemaal1 site

2026-05-21 13:22:46 +02:00

README.md

scaffold: hub-and-spoke layout, 4-network topology, 13 stack stubs

2026-05-21 12:37:59 +02:00

README.md

sites

Per-plant edge deployments. One folder per physical site.

Convention

sites/<plant>/
├── compose.yml      # include: ../../stacks/...
├── .env.example     # committed; copy to .env locally
└── README.md        # site-specific notes (IPs, LAN ranges, ops contact)

The folder name is kebab-case and matches the plant's short name (e.g. nieuwveer, bath, waalwijk).

What runs at an edge

nginx-proxy, wireguard-client, keycloak, portainer, influxdb, grafana, node-red, mqtt, postfix. Cloud-only services (gitea, jenkins, sql, wireguard-server) are not deployed at edges.

Networks (mirrors cloud, plant-LAN-facing)

Network	Notes
`edge`	nginx-proxy, bound to the plant-LAN interface only
`app`	nginx-proxy, mqtt, postfix, node-red, grafana, keycloak, wireguard-client
`data`	influxdb, grafana (`internal: true`)
`mgmt`	portainer, keycloak, wireguard-client

Ingress at edge

Port	Container	Bound to
tcp/80, 443	nginx-proxy	plant-LAN interface only

The wireguard-client publishes nothing — it dials out to the cloud server.

Creating a new site

cp -r <existing-site> sites/<new-plant> (or scaffold by hand).
Edit compose.yml for any site-specific overrides.
Edit .env.example and copy to .env with real values.
Deploy: cd sites/<new-plant> && docker compose up -d.

See ../docs/architecture.md for the full design rationale.