ops: align production ETL with legacy admin source

2026-08-09 13:53:07 +08:00
parent 664d8adbf0
commit d36ca7aac2
3 changed files with 31 additions and 6 deletions
@@ -11,6 +11,16 @@ This runbook moves production to the current reviewed `staging` release while al

 This is not a volume copy. A full Supabase dump must not be restored over the target database.

+## Confirmed migration decisions
+
+- production Owner: `luna@copse.life` / `b8907d0c-6ed0-4270-b866-7e83bb4a1b26`;
+- source Supabase project: `vtvnfqmonbfuxmqkqdlc`;
+- the legacy production `ADMIN_EMAILS` allowlist contains only the designated Owner, and the legacy database has no `public.admin_users`; the ETL seeds that attested Owner into the target admin model;
+- payment and model-provider ciphertext mode: `exclude`; re-enter both configurations after cutover with newly generated encryption keys;
+- release policy: validate on `staging`, then promote the same accepted SHA to production;
+- DNS remains unchanged until the final ETL and reconciliation pass;
+- proposed maintenance window: `2026-08-12 02:00–04:00 UTC+8`, pending operator confirmation after rehearsal timing.
+
 ## Release invariants

 The production deployment and schema-migration workflows are manual-only and accept a full lowercase 40-character `deploy_sha`. A normal production mutation proceeds only when all of the following identify that exact SHA:
@@ -30,7 +40,7 @@ Repository variables:
 | Name | Required value |
 | --- | --- |
 | `PRODUCTION_HOST` | `118.194.235.34` |
-| `PRODUCTION_PORT` | Confirmed SSH port; do not assume `22` |
+| `PRODUCTION_PORT` | `22` (confirmed on 2026-08-09) |
 | `PRODUCTION_USER` | `deploy` |
 | `PRODUCTION_PATH` | `/opt/jyotisha-production` |
 | `PRODUCTION_URL` | `https://jyotisha.chat` |