Dan's Gaming League Series
A stat tracker for DGLS — a CS2 Wingman league played in the Individual Rotating Mixer format. Because teammates rotate randomly every week, standard win/loss records are misleading. This platform surfaces individual skill through rate-based metrics, primarily ADR (Average Damage per Round).
Documentation
Full reference docs live in docs/. Start with docs/README.md for the index. Highlights:
Tech Stack
- Frontend: Next.js 16 (App Router, TypeScript, Tailwind CSS)
- Backend/Database: Supabase (PostgreSQL, REST API, DB views)
- Auth: NextAuth.js with Steam OpenID
- Deployment: Vercel (frontend + a Python function for the EHOG recompute) + Supabase cloud (DB)
Getting Started
npm install
npm run dev # http://localhost:3000
Other useful commands:
npm run build # production build (also type-checks)
npm run lint # ESLint
Development shortcut: When NODE_ENV=development, two mock login buttons appear (Dev: Zach / Dev: Dan) that skip Steam auth entirely and sign you in as a known player. You do not need STEAM_API_KEY or NEXTAUTH_URL for local dev if you use these.
Environment Variables
Create .env.local at the repo root. (In a Claude Code web session, skip this — a SessionStart
hook auto-provisions a local Supabase stack instead when .env.local is absent; see
docs/e2e.md's "Claude Code sessions" section.)
| Variable | Purpose |
|---|
NEXT_PUBLIC_SUPABASE_URL | Supabase project URL |
NEXT_PUBLIC_SUPABASE_ANON_KEY | Supabase anon key — used only by the browser's Realtime subscriptions (src/lib/supabase-browser.ts); it can read just the tables those subscriptions watch. Unset, pages render without live updates |
SUPABASE_SERVICE_ROLE_KEY | Service role key — every server-side read and write (getAdminClient()), never sent to the client |
NEXTAUTH_URL | Full base URL, e.g. http://localhost:3000 |
NEXTAUTH_SECRET | Secret for signing session tokens (any random string locally) |
STEAM_API_KEY | Steam Web API key — fetches player avatars/nicknames |
DISCORD_CLIENT_ID | Discord application client id — self-service Discord account linking (/api/auth/discord/link) |
DISCORD_CLIENT_SECRET | Discord application client secret — token exchange in /api/auth/discord/callback, server-side only |
DISCORD_MATCH_NOTIFICATIONS_WEBHOOK_URL | Discord incoming webhook URL for the #match-notifications channel — server-live and final-score alerts (src/lib/discord-notify.ts). Omit to disable; every call site no-ops without it |
DISCORD_PUBLIC_KEY | Discord application public key — verifies incoming slash-command requests to /api/discord/interactions (src/lib/discordInteractions.ts) |
DISCORD_APPLICATION_ID | Discord application id — used only by scripts/register-discord-commands.ts to register/update the slash command definitions |
DISCORD_BOT_TOKEN | Discord bot token — grants/revokes @Participants and manages per-player name-color roles (src/lib/discord-roles.ts, #397), publishes weekly match threads and closes them once played (src/lib/discord-threads.ts, #398), scans each match thread's message history for a shared scheduled event and syncs its start time into scheduled_at (src/lib/discord-event-sync.ts, #398), and registers slash commands (); the interactions endpoint itself is verified by , not this token. Needs , , , (to archive/lock a played match's thread), and (to scan a thread for a shared event), plus a channel-level permission overwrite on each season's forum channel if it restricts access — with the bot's own role positioned at the top of the server's role hierarchy, above and above where name-color roles get created. Reading guild scheduled events needs no extra permission beyond guild membership |
For the route table, schema, API endpoints, and deployment details, see docs/architecture.md. For the Python ingestion pipeline, see ingestion/README.md.
