From 853f09320c40af29874a07d1a2e6d5f12441958c Mon Sep 17 00:00:00 2001 From: Claude Opus 5 Date: Sun, 6 Sep 2026 10:01:17 +0200 Subject: [PATCH] =?UTF-8?q?docs:=20probed=200pt.app=20=E2=80=94=20Vercel?= =?UTF-8?q?=20answers=20with=20HTTP=20402=20DEPLOYMENT=5FDISABLED?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The previous commit said "nobody has probed the running site". I then probed it, so the docs should not keep hedging. curl -sI https://0pt.app/ HTTP/2 402 server: Vercel x-vercel-error: DEPLOYMENT_DISABLED strict-transport-security: max-age=63072000 https://0pt.app/api/health -> HTTP 402, body "Payment required / DEPLOYMENT_DISABLED" Two facts hold simultaneously and the docs now state both: the Coolify deploy hook fires for real on every push to main, AND the public product domain is dark behind a disabled Vercel deployment with DNS never cut over. Neither cancels the other. Still not established, and still marked as such: whether the Coolify app builds and starts. A deploy endpoint returning 200 means the request was accepted, not that a container came up healthy. Side note worth recording for PR #19: the HSTS header on that 402 response is Vercel's platform default, which is exactly the disappearing-on-cutover risk next.config.mjs in PR #19 was written to remove. Co-Authored-By: Claude Opus 5 --- README.md | 6 +++--- docs/02-architecture.md | 10 +++++++--- docs/compliance/GOLDEN-STANDARD-REPORT.md | 2 +- 3 files changed, 11 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index a40a8c3..86d318c 100644 --- a/README.md +++ b/README.md @@ -74,9 +74,9 @@ cd services/api && pip install -r requirements.txt && uvicorn orchestrator.main: `main` at `1ff34410` (2026-09-06): job `Deploy to Coolify / deploy` (run 11695, job 26295) finished **success** with `coolify deploy HTTP 200` in its log. **Every merge into `main` now fires a real redeploy against `cloud.siax.io` — know what you are shipping before you merge.** - Still *not* verified by anyone: whether that Coolify app actually builds, starts and serves, and - whether `0pt.app` DNS points at it or still at Vercel. Nobody has probed the running site, so - treat "which host answers `0pt.app`" as an open question rather than assuming either answer. + **Probed 2026-09-06 08:00 UTC:** `0pt.app` still answers from **Vercel** (`server: Vercel`, `x-vercel-id: arn1::…`) and returns **HTTP 402 `DEPLOYMENT_DISABLED` — "Payment required"** on both `/` and `/api/health`. So the public domain is *down*, DNS has **not** been cut over to Coolify, and the Coolify app — whatever state it is in — serves no `0pt.app` traffic. Two separate facts, both true at once: the deploy hook fires for real, and the product domain is dark behind an unpaid Vercel deployment. + Still not established: whether the Coolify app itself builds and starts — the deploy endpoint + returning 200 only means the request was accepted, not that a container came up healthy. - **Engine + DB + embeds** → one VPS via [`infra/docker-compose.yml`](infra/docker-compose.yml) (Postgres+pgvector, Redis, api, worker, NocoDB, Metabase, Caddy). - Env inventory: [`.env.example`](.env.example). - **Auth on `/api/0pt/*` is fail-closed**: with `AUTH_ENFORCE` unset the middleware diff --git a/docs/02-architecture.md b/docs/02-architecture.md index 20b0f8d..cd987e1 100644 --- a/docs/02-architecture.md +++ b/docs/02-architecture.md @@ -220,9 +220,13 @@ Flagged so it is not repeated: `src/services/quality-check-service.ts`, `src/ser > `TODO-no-coolify-app-provisioned-yet` literal, so both guards in > `.gitea/workflows/cd.yml` pass. On the push to `main` at `1ff34410` (2026-09-06) the > `Deploy to Coolify / deploy` job finished **success** with `coolify deploy HTTP 200`. -> **Every merge into `main` fires a real redeploy against cloud.siax.io.** What is still -> unverified: whether that Coolify app builds and serves, and whether `0pt.app` DNS points -> at it or still at Vercel — nobody has probed the running site. +> **Every merge into `main` fires a real redeploy against cloud.siax.io.** +> +> Probed 2026-09-06 08:00 UTC: `0pt.app` still answers from **Vercel** (`server: Vercel`) +> with **HTTP 402 `DEPLOYMENT_DISABLED`** on both `/` and `/api/health`. The public domain +> is therefore *down*, DNS has not been cut over, and the Coolify app serves no `0pt.app` +> traffic. Still unestablished: whether the Coolify app builds and starts at all — an +> accepted deploy request is not a healthy container. - **Vercel** (Hobby/free) — Next.js + custom domain `0pt.app`. - **One small VPS** (e.g. Hetzner ~€5/mo) running `docker-compose` (`infra/docker-compose.yml`): FastAPI, workers, NocoDB, Metabase, (Postgres or use Neon), optional Meilisearch later. Per-service managed platforms (Railway) get expensive once you have 4–5 always-on services; a single VPS + Vercel + R2 lands ≈ <€10/mo to start. diff --git a/docs/compliance/GOLDEN-STANDARD-REPORT.md b/docs/compliance/GOLDEN-STANDARD-REPORT.md index d4c7c42..6de0bcf 100644 --- a/docs/compliance/GOLDEN-STANDARD-REPORT.md +++ b/docs/compliance/GOLDEN-STANDARD-REPORT.md @@ -56,7 +56,7 @@ | D1 | Container icke-root, multi-stage, utan tsx i prod | ✅ | Dockerfile: node:24-alpine, builder+runtime, `USER node`, `CMD next start` (ingen tsx) | | D2 | /health verifierar beroenden | ⚠️ | /api/health rapporterar db/queue lägen men alltid `ok:true` — liveness ej readiness; "alltid grönt för en döende instans" (ARCHITECTURE §6) | | D3 | CI grön på main | ✅ | Gitea Actions run 3759 success; deploy.yml röd men avsiktligt (guard) | -| D4 | Deploy till Coolify provisionerad | ⚠️ **(uppdaterad 2026-09-06, var ❌)** | Coolify-app ÄR provisionerad: repo-variabeln `COOLIFY_APP_ID` innehåller en riktig 24-teckens-UUID och repo-secreten `COOLIFY_TOKEN` finns (skapad 2026-08-31). Guarden i `cd.yml` passerar och deployen körde `coolify deploy HTTP 200` på push `1ff34410`. Kvarstår ⚠️ och inte ✅ eftersom ingen har verifierat att appen faktiskt bygger, startar och serverar `0pt.app` — bara att webhooken accepteras | +| D4 | Deploy till Coolify provisionerad | ⚠️ **(uppdaterad 2026-09-06, var ❌)** | Coolify-app ÄR provisionerad: repo-variabeln `COOLIFY_APP_ID` innehåller en riktig 24-teckens-UUID och repo-secreten `COOLIFY_TOKEN` finns (skapad 2026-08-31). Guarden i `cd.yml` passerar och deployen körde `coolify deploy HTTP 200` på push `1ff34410`. Kvarstår ⚠️ och inte ✅: probe 2026-09-06 08:00 UTC visar att `0pt.app` fortfarande svarar från **Vercel** med **HTTP 402 `DEPLOYMENT_DISABLED`** — publika domänen är nere, DNS är inte omlagd, och Coolify-appen serverar ingen `0pt.app`-trafik. Att webhooken accepteras (HTTP 200) betyder inte att en container kommer upp frisk | | D5 | Backup + testad restore | ❌ | Ingen backup, ingen DB i prod, restore aldrig testat (ARCHITECTURE §6) | | D6 | Loggning/observabilitet | ⚠️ | Ingen strukturerad loggning/OTel; endast console.warn (ARCHITECTURE §6) | | D7 | Infisical-projekt + token tillgängligt för denna session | ➖ | **Blockerare:** ingen Infisical-token tillhandahållen — projekt/secret-bootstrap kan inte verifieras (se SLUTRAPPORT) |