ryan
d005080aca
Hosts can optionally cap total attendance (RSVPs + plus-ones) when creating an event. Capped events require guests to log in via the existing email code flow; RSVPs are tied to accounts and deduped per user. The event page shows spots left and replaces the form with a full notice when the cap is reached; the server rejects over-cap RSVPs and edits with 409 as a race backstop. Also threads a safeNext-validated ?next= param through the login and name-setup flow so guests land back on the event after signing in. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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