FloBama OS

Public FloBama Music Hall site plus the staff operations platform. / serves the GHL AI Studio redesign (events, menu, catering, and more) with staff login at the bottom of the home page. Staff tools remain under /dashboard and other authenticated routes. It does not modify flobamadowntown.com, Pick'em, or other production systems.

Product overview: see docs/flobama-os-v1.pdf for V1 features, APIs, architecture, and database diagrams (regenerate with python3 scripts/generate-flobama-os-v1-pdf.py).

Stack

• Next.js App Router, TypeScript, Tailwind CSS, shadcn/ui
• Supabase Postgres + Auth with @supabase/ssr cookie sessions
• Zod validation, Luxon for America/Chicago scheduling

Defaults chosen for this milestone

• Single venue record: FloBama Music Hall (11111111-1111-4111-8111-111111111111)
• Timezone locked to America/Chicago in the database
• Official FloBama wordmark (public/flobama-logo.png) on staff OS, weekly flyers, and vertical kiosk screens. Warm-red #d36b4a is the matching accent.
• No public signup. The first admin is bootstrapped in SQL; later staff are created in Settings by an admin.
• Event “Publish” plus public visibility feeds the public API, HTML embed, and OBS overlay. The Google Sheet on flobamadowntown.com is not edited from this repo.

Local setup

Option A — hosted Supabase project (recommended)

1. Create a project at supabase.com/dashboard. Do not use an existing production database.
2. Copy .env.example to .env.local and fill:

cp .env.example .env.local

• NEXT_PUBLIC_SUPABASE_URL — Project Settings → API → Project URL
• NEXT_PUBLIC_SUPABASE_ANON_KEY — Project Settings → API → anon / publishable key
• SUPABASE_SERVICE_ROLE_KEY — Project Settings → API → service_role (server only; needed to create staff logins)

3. Apply the schema. SQL editor: paste the files in supabase/migrations/ in filename order.
   Needed for this app: 20240908000001_init_flobama_os.sql, 20260908000002_public_listings_and_booth.sql, 20260908000003_staff_admin.sql, 20260908000005_screens.sql, 20260908000006_week_events_slide.sql, 20260908000007_screen_takeover.sql, 20260909000008_ticketing.sql, 20260909000009_master_admin.sql, 20260909000010_layout_object_types.sql, 20260928000011_led_wall.sql, 20260929000012_trivia.sql, and 20260929000013_led_trivia_scene.sql.

   Or with the CLI after npx supabase login and npx supabase link --project-ref <ref>:

npx supabase db push

4. Authentication → URL Configuration:

• Site URL: https://flobama-os.vercel.app (keep http://localhost:43123 in Additional Redirect URLs for local)
• Redirect URLs:
  • https://flobama-os.vercel.app/auth/callback
  • https://flobama-os.vercel.app/auth/callback?next=/reset-password
  • https://flobama-os.vercel.app/reset-password
  • the same paths on http://localhost:43123

Enable email/password. The app has no staff signup screen; keep public registration off if the dashboard offers it.

5. Bootstrap the first admin (below), then npm run dev and open http://localhost:43123.

Option B — Docker on your machine

Requires Docker Desktop (or compatible) with enough RAM. This cloud workspace cannot keep the full stack running.

npm install
npm run supabase:start
npm run supabase:env
npm run dev

supabase:start applies supabase/migrations. Auth redirects are already set in supabase/config.toml for port 43123. Studio is at http://127.0.0.1:54323. Create the first user there, then run the admin SQL.

Staff roles and admin bootstrap

Role	What they can do
Admin	Create staff, change roles, rename the venue, edit events/artists, screens, ticketing, Server Station config
Manager	Edit events/artists, import listings, screens, ticketing; can open Server Station
Server	Server Station kiosk only — events lookup, approved LED scenes, temporary wall graphics
Viewer	Read-only calendar, artists, staff directory, ticketing sales. Can activate LED wall scenes

There is still no public registration. The first admin is created once:

1. In Supabase Authentication > Users, add a user with email and password. Copy the user UUID.
2. Open supabase/bootstrap_admin.sql, replace 00000000-0000-0000-0000-000000000000 with that UUID, and run it in the SQL editor.

After that, signed-in admins use Settings → Staff to create more logins (email, temporary password, role). People cannot raise their own role. You cannot remove or demote the last admin, or change your own access. [email protected] is the master admin and cannot be removed or demoted by other staff.

Creating a login needs SUPABASE_SERVICE_ROLE_KEY on the server. Role changes and removals use the signed-in admin session and RLS.

Server Station (floor kiosk)

1. Apply supabase/migrations/20261017000050_server_role.sql, then 20261017000051_server_station.sql.
2. In Settings → Server Station, approve LED scenes, set the temporary playlist, create a pairing code, and assign staff PINs.
3. On the kiosk open /server/login, enter the pairing code, then unlock with a staff PIN.
4. Admins/managers can open /server with their normal staff login.
5. CRON_SECRET (already used for LED automation) also signs Server Station staff cookies and phone upload tokens when set; otherwise the service role key is used as a fallback. No service-role credentials are stored in the browser.

Architecture notes: docs/server-station-architecture.md.

Scripts

npm run dev              # http://localhost:43123
npm run supabase:start  # local Docker stack
npm run supabase:env    # write .env.local from that stack
npm run supabase:stop
npm run build
npm run start
npm run lint
npm run typecheck
npm run test

This is the beginning of the README. Read the rest at the original. Read the full README ↗