Skip to content

Onset BWS DB Reference Validation

Date: 2026-08-29
Context: Preventive check after RealOutcomes NAMING-2 regression (REALOUTCOMES_DIRECTORY_500_DIAGNOSTIC.md). Onset app not deployed yet (T-3).

Summary

Check Result
ONSET_DB_PROD_DATABASE_URL PASS — 192.168.1.102:5432 (onset-db LAN)
ONSET_DB_PROD_SUPABASE_URL PASS — http://192.168.1.102:8000
ONSET_DB_PROD_SUPABASE_POOLER_URL PASS — 192.168.1.102:6543
Hosted pooler in DB prod keys None
push-db-stack-bws.py refresh Ran — 11 keys updated from live VM 119
T-3 deploy readiness PASS (preventive; no app container yet)

Onset did not inherit the RealOutcomes stale-copy bug. DB prod keys already pointed at LAN; refresh confirmed against live stack.

BWS key inventory (post-refresh)

Sovereign runtime (ONSET_DB_PROD_*)

Key Host / value
ONSET_DB_PROD_DATABASE_URL 192.168.1.102:5432/postgres
ONSET_DB_PROD_SUPABASE_URL http://192.168.1.102:8000
ONSET_DB_PROD_SUPABASE_POOLER_URL 192.168.1.102:6543/postgres

App build / public (ONSET_APP_PROD_*)

Key Host / value
ONSET_APP_PROD_VITE_SUPABASE_URL http://192.168.1.102:8000
ONSET_APP_PROD_NEXT_PUBLIC_SUPABASE_URL http://192.168.1.102:8000

Gate B only (not app runtime)

Key Purpose
ONSET_HOSTED_DATABASE_URL db.emxrmjysvxeboavhatry.supabase.co:5432 — intentional for hosted pg_dump / Gate B

Legacy unprefixed SUPABASE_URL (lzpyfohgfdohrtlamzek.supabase.co) may remain in BWS from pre-migration; T-3 render script must read only ONSET_APP_PROD_* + ONSET_DB_PROD_* (mirror RealOutcomes render-*-env-app.sh).

T-3 deploy note

Before first clinic deploy on VM 118:

  1. Add scripts/onset/render-onset-env-app.sh (APP + DB prefixes).
  2. Run push-db-stack-bws.py if stack .env changed.
  3. Deploy with deploy-onset-app.sh pattern — recreate container, not restart.

Expected rendered DATABASE_URL: LAN onset-db, not emxrmjysvxeboavhatry.

References