Serve the rebuild on app.coulomb.social; defer apex Bubble cutover

Document parallel-host strategy: Railiance on app.*, Bubble remains on
coulomb.social until data and self-registration are ready.
This commit is contained in:
tegwick 2026-08-09 23:20:30 +02:00
parent fe8b96a388
commit f5537d8365
4 changed files with 46 additions and 89 deletions

View file

@ -90,12 +90,15 @@ Unregistered redirects still fail with `invalid_profile_usage` (T03).
make test
```
## Blockers for production hostname smoke
## Public host (parallel to Bubble)
| Blocker | Detail |
|---------|--------|
| Public DNS | `coulomb.social` → Cloudflare `104.*` (Bubble), not `92.205.62.239` |
| TLS cert | `certificate/coulomb-social-tls` **not Ready**; HTTP-01 challenge gets **404** from public edge (LE never reaches cluster solver) |
| Secure cookies | prod `SESSION_COOKIE_SECURE=True` — need HTTPS after cutover |
**Strategy:** live Railiance app on **`app.coulomb.social`**; apex **`coulomb.social`** stays Bubble until content + self-registration cutover.
See cutover steps in `docs/deploy.md`.
| Check | Detail |
|-------|--------|
| Cluster host | `app.coulomb.social` (Helm + ingress) |
| OIDC redirect | `https://app.coulomb.social/auth/callback/` |
| DNS | operator: `app.coulomb.social` A → `92.205.62.239` |
| Apex | **do not** repoint until Bubble retirement |
See `docs/deploy.md`.