docs(env): .env.example pointed at a dashboard we retired - #807
Merged
Conversation
The managed Supabase Cloud project was decommissioned in 2026-06 — this repo documents that in docs/operations/DECOMMISSION-CLOUD.md and marks the retired host in next.config.js. But .env.example still opened with # Get from: https://supabase.com/dashboard/project/[project]/settings/api and gave the URL as a hosted placeholder. That is the first file anyone opens when setting the app up, and it sends them to a control plane we do not have. Not a cosmetic fix. The same shape took botsmann down: its setup doc described a hosted project in the present tense, so its eleven migrations were never applied and /api/health served PGRST205 for months while every deploy went green (bitbaum/botsmann#143). A wrong pointer to a real-looking place is worse than no pointer — no pointer makes someone ask, a plausible one makes them assume it was handled. Found by a fleet-wide sweep for hosted-Supabase references; this was the last live instruction left in the fleet. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018waGt1ieA9TjpscqrbrnGb
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The managed Supabase Cloud project was decommissioned in 2026-06. This repo already documents that —
docs/operations/DECOMMISSION-CLOUD.mdis the runbook, andnext.config.jsmarks the retired host in a comment. But.env.examplestill opened withThat is the first file anyone opens when setting the app up, and it sends them to a control plane we do not have.
Not cosmetic. The same shape took botsmann down: its setup doc described a hosted project in the present tense, so its eleven migrations were never applied and
/api/healthservedPGRST205for months while every deploy went green (bitbaum/botsmann#143). A wrong pointer to a real-looking place is worse than no pointer — no pointer makes someone ask, a plausible one makes them assume it was handled.Now points at
https://supabase.orangecat.ch, says the keys live in the box.env, and links the decommission runbook for the history.Found by a fleet-wide sweep for hosted-Supabase references. This was the last live instruction left in the fleet — printcraft's was deleted in bitbaum/printcraft#30, and bitbaum/fleet#4 adds the audit that keeps it that way. The runbook, the CLAUDE.md warning and the
next.config.jscomment stay exactly as they are: they are records of leaving, and the audit's baseline names them with a reason.npm run verifygreen (all 15 gates); pre-commit and pre-push hooks green.