Cricket scorer

Small Next.js app: create a match, score on the secret write URL, share the public read-only URL (/m/{public_id}). After you mark the match complete, further edits require the scorer PIN again (stored as hash; unlock uses an HttpOnly cookie).

The Sparta club website (events, RSVPs, marketing, admin) lives in a separate project: C:\Roop\Code\hobby\sparta-club-portal.

Setup

1. Copy .env.example to .env.local.
2. In Supabase: Project Settings → API — set NEXT_PUBLIC_SUPABASE_URL and SUPABASE_SERVICE_ROLE_KEY (server-only, never expose to the browser bundle in client components).
3. Set MATCH_UNLOCK_SECRET to a long random string (e.g. openssl rand -hex 32).
4. Optional NEXT_PUBLIC_SITE_URL — used for nicer absolute links locally and in production (Vercel deploy URL).

Database (Supabase)

Project: cric-score · ref lojomuhczvxyouudassi (must match NEXT_PUBLIC_SUPABASE_URL).

Full setup steps (MCP, SQL Editor, verify): supabase/README.md

First-time migration (reusable, idempotent): run
supabase/migrations/001_cricket_scorer_initial.sql
in the Supabase SQL Editor, or via Supabase MCP apply_migration with name cricket_scorer_initial.

After the project is active and migration is applied:

npm run db:verify

UI mockups (HTML/CSS)

Static design previews — open in a browser (no build step):

• mockups/index.html — overview + side-by-side previews
• mockups/live-scorer.html — scoring pad + hero score
• mockups/create-match.html — setup form
• mockups/public-scorecard.html — read-only view

Inspired by common live-score patterns (big score first, card layout, ball chips, thumb-friendly pad). Not wired to the app yet.

Scripts

npm install
npm run dev
npm run build

Hosting

Production (Vercel): https://cricket-scorer-azure.vercel.app

Project name: cricket-scorer · team: roop-yekollus-projects

Vercel env vars (already set on deploy)

Variable	Notes
NEXT_PUBLIC_SUPABASE_URL	Supabase project URL
SUPABASE_SERVICE_ROLE_KEY	Server-only
MATCH_UNLOCK_SECRET	PIN unlock signing
NEXT_PUBLIC_SITE_URL	https://cricket-scorer-azure.vercel.app

Optional: NEXT_PUBLIC_SUPABASE_ANON_KEY if you add client-side Supabase later.

Redeploy after env changes: npx vercel deploy --prod

GitHub

Repo: yrk1436/cricket-scorer (public) · branch main

If the repo is not created yet, either:

1. Open github.com/new?name=cricket-scorer and click Create repository, or
2. In Cursor → MCP → GitHub, ensure the token can create repositories (classic repo scope or fine-grained Administration write).

Then push from this folder:

git remote set-url origin https://github.com/yrk1436/cricket-scorer.git
git push -u origin main
npx vercel git connect

Or run .\scripts\publish-github.ps1 after gh auth login.

Vercel pairs well with Next.js. Remember the Supabase free tier may pause idle projects.