| name | db-local |
| description | Bring up the local Docker Postgres (activecamt-db) and run/rehearse DB operations against LOCALHOST (.env.local) — migrations, seeds, studio — never prod. Use before any migration (rehearse locally first), or to get a working local DB for tests/seed data. Encapsulates the finicky local-DB dance so you never accidentally hit prod. |
Local DB (ActiveCAMT)
Everything here targets localhost only. The danger this skill removes: npm run db:migrate
(and db:seed, db:reset) are hard-wired to --env-file=.env, and .env is PROD Supabase.
To work locally you must invoke tsx yourself with .env.local.
The local DB
- Docker container
activecamt-db (postgres:16-alpine), host port 5432, user postgres, db activecamt. It is often stopped.
- This is a standalone
docker run, NOT the db service in docker-compose.yml (that one deliberately doesn't expose 5432 and uses different creds).
Start it
docker start activecamt-db
until docker exec activecamt-db pg_isready -U postgres >/dev/null 2>&1; do sleep 1; done
If docker ps doesn't list it at all, it may need first-time creation — ask the user; don't guess credentials.
Rehearse a migration locally (safe, idempotent)
Run the SAME src/db/migrate.ts that prod runs, but against localhost:
npx tsx --env-file=.env.local src/db/migrate.ts
A clean run on an up-to-date DB is mostly ⚠️ already exists notices ending in ✅ Migration complete!. Because the script is idempotent, this is safe to run anytime and surfaces SQL errors with zero prod risk. This is the rehearsal step /safe-deploy recommends before touching prod.
Other local ops
npx tsx --env-file=.env.local src/db/seed.ts
npx tsx --env-file=.env.local src/db/reset.ts
Hard rules
- LOCALHOST ONLY. Never run anything here with
--env-file=.env. If DATABASE_URL resolves to a supabase.* host or port :6543 (the prod pooler), STOP — that's prod.
.env has its localhost line commented out; its active DATABASE_URL is the prod pooler. So --env-file=.env = prod, always. Use .env.local.src/db/guard.ts refuses db:reset/db:seed against remote/prod without CONFIRM=yes — do not work around it by pointing at prod.- For the PROD migration path (apply for real, in order, before deploy), use
/safe-deploy, not this skill.
Quick reference
| Thing | Command |
|---|
| Start local DB | docker start activecamt-db |
| Wait for ready | until docker exec activecamt-db pg_isready -U postgres >/dev/null 2>&1; do sleep 1; done |
| Rehearse migration | npx tsx --env-file=.env.local src/db/migrate.ts |
| Seed (local) | npx tsx --env-file=.env.local src/db/seed.ts |
| Prod migration | npm run db:migrate (PROD — use /safe-deploy) |
