ryan 4915af0665 Fix login on legacy DBs: drop NOT NULL phone/email from verification_codes
Old prod DBs had verification_codes.phone (or email) as NOT NULL with no
default, so inserting a code via identifier-only failed silently — users
received an emailed code that was never stored, and verify always said
"Invalid or expired code." Drop the legacy columns in a migration and
stop swallowing the CreateVerificationCode error.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-06-10 19:07:18 -04:00
2026-05-14 22:55:54 -04:00
2026-05-14 22:55:54 -04:00
2026-05-14 22:55:54 -04:00
2026-05-22 23:05:17 -04:00
2026-05-22 23:05:17 -04:00
2026-05-14 22:55:54 -04:00

bbq

Potluck signup app. No accounts — share a link, people claim slots.

Run locally

go build -o bbq . && ./bbq

Listens on :8080. Set PORT and BBQ_DB env vars to override.

Docker

docker compose up -d --build

Runs on 127.0.0.1:8090. Data persists in a bbq-data volume.

Reverse proxy (Caddy)

bbq.example.com {
    reverse_proxy localhost:8090
}

Regenerate DB layer

$(go env GOPATH)/bin/sqlc generate
S
Description
No description provided
Readme 309 KiB
Languages
Go 60%
HTML 39.4%
Dockerfile 0.4%
Makefile 0.2%