Local Supabase config added for one-command dev setup

andrsschultz added a `supabase/` directory with `config.toml`, a one-shot schema migration, and a runbook, replacing the previous "paste this SQL into the Supabase editor" onboarding. A few rough edges to watch for before adopting.

infrastructure

The new supabase/ directory contains config.toml, migrations/000_one_shot_schema.sql, seed.sql, README.md, and a .gitignore. Running npx supabase start spins up the local stack; npx supabase status prints the keys to paste into .env files. Both .env.example files now default to http://127.0.0.1:54321 instead of https://your-project.supabase.co.

Two things to fix before adopting. First, config.toml sets the database port to 55422 instead of Supabase's default 54322 - the commit says this avoided a collision on andrsschultz's machine, so it should be reverted to 54322 for general use. Second, the schema file is a copy of backend/migrations/000_one_shot_schema.sql, meaning the tree now has two copies that can diverge. Worth setting up a lint check or replacing one with a symlink.

The GSJ-Master entry added to .gitignore looks like a personal artifact name; ignore it.

No application code changed. This is purely config and docs.

So what Worth adopting if you want `npx supabase start` to be the full local setup step. Fix the port back to `54322` and deal with the schema duplication before committing to the approach.

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from andrsschultz/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`d354c310`	Add local Supabase config and one-shot migration	asschultz	2026-04-30	↗ GitHub
commit body Add a supabase/ directory with local Supabase runbook and config: config.toml (custom ports/API URL), migrations/000_one_shot_schema.sql (one-shot DB schema), seed.sql, README.md, and a supabase/.gitignore. Update docs and examples to prefer local Supabase: README updated with startup and key extraction steps and AIRGAP.md mention; backend/.env.example and frontend/.env.local.example now reference the local SUPABASE_URL and placeholder local keys. Also add GSJ-Master to .gitignore. This enables easy local development with npx supabase start and a fresh database initialized from the provided one-shot migration.

SHA

Subject

Author

Date

d354c310

Add local Supabase config and one-shot migration

asschultz

2026-04-30

↗ GitHub

commit body

Add a supabase/ directory with local Supabase runbook and config: config.toml (custom ports/API URL), migrations/000_one_shot_schema.sql (one-shot DB schema), seed.sql, README.md, and a supabase/.gitignore. Update docs and examples to prefer local Supabase: README updated with startup and key extraction steps and AIRGAP.md mention; backend/.env.example and frontend/.env.local.example now reference the local SUPABASE_URL and placeholder local keys. Also add GSJ-Master to .gitignore. This enables easy local development with npx supabase start and a fresh database initialized from the provided one-shot migration.

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-83.md from inside the repo you want the changes in.