4 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
Fredrik JohanssonandClaude Sonnet 5	7acb0e129a	Add favicon ... Small bingo-grid mark in the shared mono-green style used by sibling projects. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-19 19:50:32 +02:00
Fredrik Johansson	cb969133ce	Document all four redirect URIs, not just the two local dev ones ... Spent a real debugging session chasing a "not matching configuration" error assuming it was host mode, when it was actually guest PKCE mode hitting a redirect URI (production, root path) that was simply never registered — the README only documented the two local dev URIs, not that host mode and guest mode each need their own entry per environment (four total), and gave no way to tell which flow's request was actually failing. Added the full four-URI table and a note to check the browser's actual address bar at the point of failure — the error message is identical regardless of which flow's redirect_uri didn't match.	2026-07-18 22:27:21 +02:00
Fredrik Johansson	dc90e7404b	Serve Spotify client ID from /api/config instead of baking it in at build ... Was a Vite build-time env var, requiring a second copy of a non-secret value as a separate Gitea CI secret alongside the one already in .env for the api service. Client id isn't sensitive (public in every Spotify authorize URL), so it doesn't need build-time baking at all — now fetched once from a new GET /api/config on the already-running api server, cached client-side after the first call. Collapses config back down to the one place it already lived (the deploy host's .env / docker-compose environment), removes the CI build-arg and its secret entirely. Verified end-to-end: /api/config returns the real client id, and a live guest-login click correctly carries it through into the actual Spotify authorize URL (decoded and checked, not just assumed from the code).	2026-07-18 22:15:13 +02:00
Fredrik Johansson	d99c44cb9d	Initial build: fullhouse, live music bingo from a real Spotify playlist ... Based on bingo-bango by f8al (MIT) — same core card-generation idea ("both facets": a square is either an exact song title or an artist, and an artist square lights up on any of their tracks), reworked with a real host/guest split, live multiplayer sessions, and cover-art squares. f8al credited in the footer, README, and PROPOSAL.md. Three ways to play: host a live session (server-side Spotify connection, join code + QR, caller screen, auto-call from real playback), join someone else's session (no login needed), or solo (guest PKCE login or a pasted public playlist URL, one-off card). Genuinely verified against a real Spotify account throughout, not just built and assumed working — including two real bugs found and fixed along the way (Spotify's playlist-tracks endpoint quietly renamed to /items with a reshaped response; reading playlist tracks needs real user auth even for public playlists, so the "no guest login" public-playlist path routes through the host's connection instead of a dead-end app-only token). Both Docker images built and run together on a real network with the nginx proxy verified working end-to-end, and auto-call confirmed detecting an actual track playing live through Spotify Connect within one poll tick.	2026-07-18 22:05:37 +02:00