GoNext

A VALORANT Premier coordinator for my own team: see who is available, who is confirmed, and get Discord pings so five players show up on match day.

Live app: gonext.murtazalol.com

What it does

• Discord login. Sign in with your Discord account, no passwords.
• Invite link teams. The only way onto a team is its invite link. The first person to join becomes the Coach, who can share the link from the Roster page.
• Roster and availability. Everyone sees the roster and the week's matches, and each player can edit only their own row. Players mark days as Confirmed, Tentative, or Not set.
• Roles. Players and Coaches, plus Admins who manage every signed in user from a hidden /admin page.
• Automatic Discord pings. A Discord bot posts match day reminders, a 30 minute warning before a match, and a Sunday reminder for anyone with days not set next week. All times are Eastern.

Under the hood

• Auth.js with Discord OAuth. Admin access is granted by Discord user id through an environment variable, and the /admin page returns a 404 for everyone else.
• Postgres through Prisma's node-postgres driver adapter, with Prisma migrations and seed data.
• Integration tests run against a real Dockerized Postgres instead of mocks, including a join race test that only means something against real transaction behavior.
• A bot API, GET /api/bot/pings, protected by a shared secret. The bali-bot Discord bot polls it and posts each ping once, tracked by key.
• Deployed on Vercel with Supabase Postgres.

Stack: Next.js, TypeScript, Prisma, PostgreSQL (Supabase), Auth.js, Vitest, Docker, Vercel

Development

Database is Postgres (via Prisma's node-postgres driver adapter) — see Deployment below to provision one. Once you have DATABASE_URL / DATABASE_URL_UNPOOLED in .env:

npm install
npx prisma migrate dev   # applies the schema
npx prisma db seed       # seeds the team (empty roster) and this week's matches
npm run dev

See CONTEXT.md for the domain glossary.

Testing

Tests that touch the database run against a real local Postgres (via Docker), not a mock — some of them (like the join-race test) only mean anything against real transaction behavior.

npm run test:db:up   # starts a throwaway Postgres on localhost:55432
npm test             # pushes the schema to it and runs the suite
npm run test:db:down # tear it down when you're done

Login uses Discord OAuth via Auth.js. AUTH_SECRET is already generated for you in .env.local; you need to supply the two Discord values yourself:

1. Go to the Discord Developer Portal and create a new application.
2. Under OAuth2 → General, copy the Client ID and Client Secret.
3. Under OAuth2 → Redirects, add: http://localhost:3000/api/auth/callback/discord (add your production callback URL here too once deployed, e.g. https://your-app.vercel.app/api/auth/callback/discord)
4. Paste both values into .env.local (already gitignored):

   AUTH_DISCORD_ID="your client id"
   AUTH_DISCORD_SECRET="your client secret"
   

5. Restart npm run dev.

The roster starts empty — there's no manual "add teammate" step. The only way onto the team is the invite link: visit /join/{team's invite token} (find the token by checking the seeded Team row, e.g. via npx prisma studio), sign in with Discord, and you're on the roster as yourself. The first person to join a team becomes its Coach, who can then find and share the real invite link from the Roster page. Only your own row is ever editable; everyone else's stays read-only.

Admins manage every signed-in user from /admin (hidden from everyone else — it 404s). Admin is granted by Discord user id, via an environment variable rather than the database:

1. In Discord, enable Settings → Advanced → Developer Mode, then right-click your name → Copy User ID.
2. Add it to .env.local (and the Vercel project's environment variables for production), comma-separating multiple admins:

   ADMIN_DISCORD_IDS="123456789012345678"
   

3. Restart the server (or redeploy), then log in with that Discord account — an Admin tab appears in the nav.

An Admin can add anyone who has signed in with Discord but isn't on the team yet (so new players just need to log in once), remove/reactivate anyone including Coaches, promote or demote Coaches, and regenerate the invite link.

The site tells the Discord bot (bali-bot) what to post via GET /api/bot/pings, protected by a shared secret. The bot polls it every few minutes and posts each ping once (it remembers each ping's key). What goes out, all in Eastern time:

• Match day (from noon, or 4h before an earlier match): @s confirmed teammates, says how many more are needed for five, and @s Tentative / Not set teammates to fill in.
• 30 minutes before a match: @s confirmed teammates to get online, plus Tentative / Not set ones if the team is short.
• Sunday from 6PM: @s anyone with days not set next week.

Setup:

1. Generate a secret (openssl rand -base64 33) and set it as BOT_API_SECRET in .env.local and the Vercel project's environment variables.
2. In the bot's environment, set GONEXT_URL (e.g. https://your-app.vercel.app) and the same value as GONEXT_BOT_SECRET.
3. In Discord, run /premier set-channel in the team's server.

1. Push to GitHub — the repo already has a remote (origin); commit and push main.
2. Create the Vercel project at vercel.com/new, importing this GitHub repo. Framework preset (Next.js) is auto-detected.
3. Add a Postgres database: create a free project at supabase.com, then open Connect and copy two connection strings into the Vercel project's environment variables:
   • DATABASE_URL — the Transaction pooler string (port 6543), used by the app
   • DATABASE_URL_UNPOOLED — the Session pooler string (port 5432), used by migrations
4. Set the remaining environment variables in the Vercel project settings (Production environment):
   • AUTH_SECRET — generate a fresh one (openssl rand -base64 33), don't reuse the dev value
   • AUTH_DISCORD_ID / AUTH_DISCORD_SECRET — same Discord app as local dev
   • AUTH_URL is not needed — Auth.js auto-detects the host on Vercel
5. Add the production redirect URI in the Discord Developer Portal (OAuth2 → Redirects): https://<your-vercel-domain>/api/auth/callback/discord
6. Run the migration against the new database (locally, pointed at the Supabase URLs, or via vercel env pull first): npx prisma migrate deploy && npx prisma db seed
7. Deploy — pushing to main triggers it automatically once the Vercel project is linked.

No custom domain needed for a beta — the default *.vercel.app URL is fine.