Files
nuzlocke-tracker/.beans/archive/nuzlocke-tracker-2561--supabase-auth-project-setup-and-provider-config.md
Julian Tabel a6cb309b8b
All checks were successful
CI / backend-tests (push) Successful in 28s
CI / frontend-tests (push) Successful in 28s
chore: archive 42 completed/scrapped beans
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-20 21:31:23 +01:00

22 lines
860 B
Markdown

---
# nuzlocke-tracker-2561
title: Supabase Auth project setup and provider config
status: completed
type: task
priority: normal
created_at: 2026-03-20T15:28:08Z
updated_at: 2026-03-20T20:04:40Z
parent: nuzlocke-tracker-d98o
---
Set up Supabase project with Auth enabled. Configure Google and Discord as social login providers. Add Supabase URL and keys to backend/frontend environment variables. This is the foundation — nothing else can start until the Supabase project exists.
## Checklist
- [ ] Create Supabase project (or configure existing one)
- [ ] Enable email/password auth
- [ ] Configure Google OAuth provider
- [ ] Configure Discord OAuth provider
- [x] Add SUPABASE_URL, SUPABASE_ANON_KEY, SUPABASE_JWT_SECRET to backend env
- [x] Add VITE_SUPABASE_URL, VITE_SUPABASE_ANON_KEY to frontend env
- [x] Document setup steps for local development