Snapshot both servers: the VPS catalog moves to server/vps, the home server joins as server/home

The catalog in server/containers had drifted from the VPS. Eleven compose
files and twelve units no longer matched what runs, and two running
services, Gbrown_Agent and BillTracker, were missing. server/vps is now a
copy of the live files, and panama-server reads from it.

server/home holds the home server's services in the same shape. They still
run under Docker, so the podman units there are drafts for a later move, and
nothing installs from that tree. PostHog, Sentry and Plausible are checkouts
of upstream repositories. Only their local files are kept, next to an
UPSTREAM file naming the repository and the exact commit.

Every secret in both trees is a ${VAR} reference named in .env.example, or
CHANGE_ME in files that are not compose files. The live servers still hold
some of those values inline, so a live file can differ from its copy on
those lines alone. Existing .env.example files keep their comments, with new
keys appended at the end.

The ignore rules and the secrets contract now cover both trees, plus the
volume/ and volumes/ directories the home server uses.

server/vps/Adminer/compose.yml

@@ -0,0 +1,44 @@
+# Adminer — database admin UI. VPS (ROOTLESS PODMAN), added 2026-08-12.
+#
+# On the home server this shipped alongside a MySQL container in the same compose
+# file. Here it is standalone and defaults to the shared PostgreSQL instance, which
+# is where the 14 databases now live (authentik, infisical_db, n8n, npm, the payload_*
+# and convex databases, usesend, lashaddict-payload, spoon_convex...).
+#
+# MySQL stays on the home server — nothing on the VPS uses it.
+#
+# It can still reach any other database reachable on nginx-bridge; ADMINER_DEFAULT_SERVER
+# only pre-fills the server field on the login form.
+#
+# ⚠️ SECURITY: Adminer has NO authentication of its own — it is a login form that
+# forwards credentials to whichever database you name. Publishing it means exposing a
+# database login prompt to the internet. Put it behind authentik forward-auth in NPM
+# (same pattern as sonarr/prowlarr on the home server), or restrict it to the LAN by
+# giving it only a UniFi record and no Cloudflare record.
+#
+# Rootless adaptations: no bind mounts (stateless, so no :Z needed), no published
+# ports — NPM proxies to http://adminer:8080 over nginx-bridge.
+#
+# NPM: adminer.gbrown.org -> http://adminer:8080
+
+networks:
+  nginx-bridge:
+    external: true
+
+services:
+  adminer:
+    image: docker.io/library/adminer:latest
+    container_name: adminer
+    hostname: adminer
+    domainname: adminer.gbrown.org
+    networks:
+      - nginx-bridge
+    environment:
+      - TZ=America/New_York
+      # Pre-fills the server field; any nginx-bridge host can still be typed in.
+      - ADMINER_DEFAULT_SERVER=postgresql
+      - ADMINER_DESIGN=dracula
+    labels:
+      com.centurylinklabs.watchtower.enable: "true"
+    tty: true
+    restart: unless-stopped

server/vps/Adminer/podman-adminer.service

@@ -0,0 +1,21 @@
+[Unit]
+RequiresMountsFor=/home/gib/Media
+Description=Podman Compose: Adminer
+After=network-online.target podman.socket podman-postgresql.service
+Wants=network-online.target podman-postgresql.service
+StartLimitIntervalSec=300
+StartLimitBurst=3
+
+[Service]
+Type=oneshot
+WorkingDirectory=%h/Server/Adminer
+ExecStart=/usr/bin/podman compose up -d
+ExecStop=/usr/bin/podman compose down
+RemainAfterExit=yes
+TimeoutStartSec=300
+TimeoutStopSec=60
+Restart=on-failure
+RestartSec=30
+
+[Install]
+WantedBy=default.target