Skip to content
supapuck-cms

Commands and checks

Running

Section titled “Running”
Terminal window
npx supabase start                      # local stack (ports in supabase/config.toml)
npx astro dev --background              # http://localhost:4321

Content and users

Section titled “Content and users”
Terminal window
npm run seed                            # starter templates, home page, sample event (skips what exists)
npx tsx --env-file=.env scripts/create-editor.ts you@example.org 'password' [editor|admin]
npx tsx --env-file=.env scripts/migrate-content.ts [--dry-run]   # site then core content migrations
npx tsx --env-file=.env scripts/media-formats.ts                 # backfill AVIF/WebP for existing media
npx tsx --env-file=.env scripts/copy-storage.ts                  # local storage to a hosted project

Database

Section titled “Database”
Terminal window
npx supabase db push --linked           # apply migrations to the hosted project
npx supabase db push --linked --include-all   # including out-of-order ones
npx supabase db query --linked          # run SQL against it

Checks

Section titled “Checks”
Terminal window
npm run check                                       # typecheck
npx tsx scripts/checks/recurrence.ts                # recurrence rules, DST, event date sync
npx tsx scripts/checks/formatting.ts                # autop/texturize against scripts/checks/formatting-cases.json
npx tsx scripts/checks/mailing.ts                   # mailing emails, signed links, click verdicts, digest times
npx tsx --env-file=.env scripts/mailing-e2e.ts      # mailing through the running site, without Mailgun
npx tsx --env-file=.env scripts/publishing-e2e.ts   # drafts, preview, publish

The e2e scripts (scripts/*-e2e.ts, scripts/checks/compose.ts) sign in as LOCAL_ADMIN_EMAIL / LOCAL_ADMIN_PASSWORD. They were written against a site with content (pages, events, venues, members), so on the example site some need that content first.