ryan cf2ef77bb0 Add yes/no RSVP answers with required login
RSVPs now carry a status ('yes'/'no'). When auth is enabled, answering
requires login for all events, not just capped ones. Answers are deduped
one per user and re-answering updates in place. A 'no' zeroes plus_one,
is excluded from Going counts and cap math, frees the person's slot
claims, and shows in a separate "Can't make it" list.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-26 07:59:33 -04:00
2026-05-14 22:55:54 -04:00
2026-07-13 17:21:01 -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 337 KiB
Languages
Go 60.9%
HTML 38.5%
Dockerfile 0.4%
Makefile 0.2%