Accounts need Firebase
The app is deployed and working. All 489 tracks across 37 releases are browsable, searchable and playable right now — the catalog ships with the code rather than living in a database.
What needs Firebase is the per-user half: accounts, playlists, liked songs, listening history and saved guitar tabs.
Browse the catalog anyway1 — Enable the services
In the Firebase console, turn on Authentication → Email/Password and create a Cloud Firestore database.
2 — Add the web config
From Project settings → General → Your apps. These are not secrets — a web config identifies a project, it doesn’t grant access to it.
NEXT_PUBLIC_FIREBASE_API_KEY=… NEXT_PUBLIC_FIREBASE_AUTH_DOMAIN=…firebaseapp.com NEXT_PUBLIC_FIREBASE_PROJECT_ID=… NEXT_PUBLIC_FIREBASE_APP_ID=…
3 — Give the server credentials
On Firebase App Hosting this is automatic — the Cloud Run service already runs as a service account. Anywhere else, set
FIREBASE_SERVICE_ACCOUNTto the contents of a service-account key file.4 — Publish the security rules
They scope every document to its owner, so one user can never read another’s playlists or tabs.
firebase deploy --only firestore:rules
Full notes in docs/13-firebase.md. There is no seed step any more — the catalog is code, so a fresh environment is correct the moment it boots.