feat: add Geddes Docker image for permanent Postgres+PostgREST deploy…

geddes/Dockerfile

@@ -0,0 +1,38 @@
+# ─── Birck Digital Twin — Geddes Postgres + PostgREST image ───────────────────
+#
+# Extends the official PostGIS image with the PostgREST binary baked in so
+# the API layer survives container restarts without manual re-installation.
+#
+# Build:
+#   docker build -t geddes-registry.rcac.purdue.edu/<YOUR_GROUP>/dt-postgres-postgrest:v1 .
+#
+# Push:
+#   docker push geddes-registry.rcac.purdue.edu/<YOUR_GROUP>/dt-postgres-postgrest:v1
+# ──────────────────────────────────────────────────────────────────────────────
+
+FROM postgis/postgis:16-3.4
+
+ARG POSTGREST_VERSION=v13.0.6
+
+# Install PostgREST static binary
+RUN apt-get update && \
+    apt-get install -y --no-install-recommends wget xz-utils && \
+    wget -q "https://github.com/PostgREST/postgrest/releases/download/${POSTGREST_VERSION}/postgrest-${POSTGREST_VERSION}-linux-static-x86-64.tar.xz" \
+         -O /tmp/postgrest.tar.xz && \
+    tar -xf /tmp/postgrest.tar.xz -C /usr/local/bin/ && \
+    chmod +x /usr/local/bin/postgrest && \
+    rm /tmp/postgrest.tar.xz && \
+    apt-get remove -y wget xz-utils && \
+    apt-get autoremove -y && \
+    rm -rf /var/lib/apt/lists/*
+
+# Copy PostgREST configuration (values can be overridden via env-vars at runtime)
+COPY postgrest.conf /etc/postgrest/postgrest.conf
+
+# Copy custom entrypoint that starts both Postgres and PostgREST
+COPY entrypoint.sh /usr/local/bin/dt-entrypoint.sh
+RUN chmod +x /usr/local/bin/dt-entrypoint.sh
+
+EXPOSE 5432 3000
+
+ENTRYPOINT ["/usr/local/bin/dt-entrypoint.sh"]

geddes/README.md

@@ -0,0 +1,95 @@
+# Geddes — Postgres + PostgREST Docker Image
+
+This folder contains the files needed to build a **permanent, self-healing**
+deployment of PostgreSQL (PostGIS) + PostgREST on the Purdue Geddes cluster.
+
+## Why this exists
+
+Previously, PostgREST was installed manually inside the running Postgres
+container with `apt install` + `nohup postgrest &`. Since Docker containers are
+ephemeral, every container restart wiped out the installation, causing the
+`502 Bad Gateway` error you see in the Azure Function logs.
+
+This image bakes PostgREST directly into the Docker image so it starts
+automatically on every container restart — no human intervention required.
+
+---
+
+## Files
+
+| File | Purpose |
+|------|---------|
+| `Dockerfile` | Extends `postgis/postgis` with the PostgREST binary |
+| `postgrest.conf` | Default PostgREST configuration (DB URL, schemas, role, JWT secret) |
+| `entrypoint.sh` | Starts Postgres in background → waits → starts PostgREST in foreground |
+
+---
+
+## Usage
+
+### 1. Build the image
+
+```bash
+cd geddes/
+
+docker build \
+  -t geddes-registry.rcac.purdue.edu/<YOUR_GROUP>/dt-postgres-postgrest:v1 \
+  .
+```
+
+Replace `<YOUR_GROUP>` with your Geddes registry namespace (e.g. `nanohub`).
+
+### 2. Push to Geddes registry
+
+```bash
+docker login geddes-registry.rcac.purdue.edu
+
+docker push geddes-registry.rcac.purdue.edu/<YOUR_GROUP>/dt-postgres-postgrest:v1
+```
+
+### 3. Update the Rancher Deployment
+
+In Rancher:
+1. Go to **Workloads → Deployments → `dt-postgres`**
+2. Click **Edit Config**
+3. Change the **Container Image** to:
+   ```
+   geddes-registry.rcac.purdue.edu/<YOUR_GROUP>/dt-postgres-postgrest:v1
+   ```
+4. Click **Save**
+
+Kubernetes will roll out the new pod. PostgREST will start automatically every
+time the pod restarts from now on.
+
+---
+
+## Overriding secrets at runtime (recommended for production)
+
+Instead of hardcoding credentials in `postgrest.conf`, set Kubernetes Secrets
+and pass them as environment variables. PostgREST reads any `PGRST_*` env-var:
+
+```yaml
+env:
+  - name: PGRST_DB_URI
+    valueFrom:
+      secretKeyRef:
+        name: dt-postgres-secret
+        key: db-uri
+  - name: PGRST_JWT_SECRET
+    valueFrom:
+      secretKeyRef:
+        name: dt-postgres-secret
+        key: jwt-secret
+```
+
+---
+
+## Ports
+
+| Port | Service |
+|------|---------|
+| 5432 | PostgreSQL |
+| 3000 | PostgREST HTTP API |
+
+The existing Geddes Ingress (`dt-nanohub`) already routes external HTTPS
+traffic → port 3000, so no Ingress changes are needed.

geddes/postgrest.conf

@@ -0,0 +1,19 @@
+# PostgREST configuration for the Birck Digital Twin Geddes deployment.
+#
+# These values are baked in as defaults. In production you should override the
+# sensitive ones (db-uri, jwt-secret) via Kubernetes Secrets injected as
+# environment variables (PGRST_DB_URI, PGRST_JWT_SECRET) rather than editing
+# this file directly.
+#
+# Full reference: https://postgrest.org/en/stable/references/configuration.html
+
+db-uri        = "postgres://glance:glance_secret@localhost:5432/logger"
+db-schemas    = "public"
+db-anon-role  = "glance_public"
+jwt-secret    = "test_secret_that_is_at_least_32_characters_long"
+
+# PostgREST listens on this port; Ingress/nginx will proxy 443 → 3000
+server-port   = 3000
+
+# Enable schema cache auto-reload via NOTIFY pgrst
+db-channel-enabled = true