Add infrastructure skeleton for review (refs #21)

Lays out the agreed shape from the design discussion: one flake at the root with three nixosConfigurations (mqtt-ingest, db-host, app-host), vendored Supabase docker-compose pointed at the external db-host, Caddy → Kong → PostgREST/GoTrue, a Go MQTT→Postgres ingester stub, deploy-rs node map, and a Gitea Actions workflow that deploys in db → app → ingest order on push to main. No real implementation yet — every host module has TODOs marking the gaps (real hardware config, actual hostnames, HiveMQ packaging, vendor the full upstream Supabase compose, etc.).
2026-05-27 17:23:02 +00:00
parent 71d74d3b83
commit 2d57db8182
34 changed files with 1005 additions and 0 deletions
@@ -0,0 +1,25 @@
+{ inputs }:
+
+let
+  mkNode = name: hostname: {
+    inherit hostname;
+    sshUser = "deploy";
+    user = "root";
+    profiles.system = {
+      path = inputs.deploy-rs.lib.x86_64-linux.activate.nixos
+        inputs.self.nixosConfigurations.${name};
+    };
+  };
+in
+{
+  sshOpts = [ "-o" "StrictHostKeyChecking=accept-new" ];
+  autoRollback = true;
+  magicRollback = true;
+
+  nodes = {
+    # Order matters: the Gitea Actions workflow invokes them in this sequence.
+    db-host     = mkNode "db-host"     "db-host.gebos.internal";     # TODO: real address
+    app-host    = mkNode "app-host"    "app-host.gebos.internal";    # TODO: real address
+    mqtt-ingest = mkNode "mqtt-ingest" "ingest.ge-bos.de";
+  };
+}