Use Zwift Click, Zwift Play, Shimano Di2, or any Bluetooth controller with MyWhoosh, Rouvy, Zwift, and more. Free to try on iOS, Android, Windows, and macOS.
8h +1★ 648Sports & fitness
Do you operate this project?
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Organization repository · verify with a repository file
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
A modern platform to organize and manage amateur 7-a-side football leagues. It lets teams register, schedules matches automatically, shows results and stats, and includes tools for league admins. Built as a real-world style project to practice and showcase web development skills.
Aalto Football is a web app for pick-up football in Bergen, Norway.
Hosts create matches (pitch, time, format, level and spots) and players find them and join.
Think Playtomic, but for 5-, 7-, 9- and 11-a-side football.
The site is in English by default, with Norwegian (bokmål) available through the language switcher.
It can be installed on a phone's home screen as a PWA.
Status: in development. Players can sign up, find matches, join or leave (with a waitlist), and hosts can
create, edit, cancel and share matches. Online payments are disabled for now (see Roadmap).
Requirements: Node.js 20+ and, for a local database, Docker.
git clone https://github.com/agustinsoares/futbol-7.git
cd futbol-7
# Local Supabase (Postgres + Auth + API) with the migrations and Bergen seed data
npx supabase start # prints the local API URL and publishable key
cd apps/web
cp ../../.env.example .env.local # paste the local URL and publishable key
npm install
npm run dev # http://localhost:3000
Seed users get a random password. To log in locally, set one:
psql postgresql://postgres:[email protected]:54322/postgres \
-c "update auth.users set encrypted_password = extensions.crypt('local-pass-123', extensions.gen_salt('bf')) where email like '%@aaltofootball.test'"
Without Supabase variables the site still runs and shows sample matches.
Useful commands (from apps/web):
npm run lint # ESLint
npm run typecheck # TypeScript
npm run format # Prettier
npm test # unit tests (Vitest)
npm run build # production build
npm run test:e2e # end-to-end tests (Playwright) against a running app + local Supabase
CI runs all of the above, plus the migrations against Postgres and the end-to-end suite against a local Supabase.
🗄️ Database (Supabase)
Project: yqtxllyhmmwgvvirlput (organisation Aalto Football). Migrations and sample data are already applied.
To set up a new project:
Apply the migrations in supabase/migrations/ in order (SQL editor or supabase db push).
Optionally run supabase/seed.sql for Bergen sample data. It creates [email protected] (admin),
[email protected] (regular user) and 20 more players, 7 pitches and 12 matches.
Users get a random password: set one from Authentication → Users to log in with them.
Put the project URL and publishable key in apps/web/.env.production (public values) and in .env.local for development.
Security model:
Visitors see public matches, pitches and how many spots are left. Names, profiles and who plays each match are only visible to signed-in users.
Private matches never appear in listings (not even through the API): only the host, its players and admins list them, and anyone with the link opens them with get_match().
Limits against spam live in the database (30 new matches a day, 10 chat messages a minute per person).
Only admins manage pitches and change roles (from Admin → Admins; nobody can remove their own admin role).
Joining and leaving happen only through join_match / leave_match, which lock the match row so the last spot can't be taken twice, and move the first waitlisted player up when someone drops out.
Redirect URLs: add https://<your-domain>/** and https://*-<your-vercel-team>.vercel.app/** (for previews).
Google sign-in (optional): enable the Google provider in Supabase and set NEXT_PUBLIC_AUTH_GOOGLE_ENABLED=true.
Emails: Supabase's built-in email service is heavily rate-limited; configure custom SMTP before launch
so confirmation and sign-in links reach everyone.
Email templates: branded English/Norwegian templates live in supabase/templates/ (used automatically by
local Supabase). In production, paste them in Authentication → Emails → Templates:
confirmation.html → Confirm sign up and magic_link.html → Magic link. Their links use token_hash, so
they work even when opened on a different device or browser than the one used to sign up.
Also recovery.html → Reset password (subject Reset your Aalto Football password).
Reminder emails and daily job
vercel.json schedules /api/cron/daily once a day (06:00 UTC). It marks finished matches as played and emails
confirmed players whose match starts in the next 26 hours. Set these environment variables in Vercel:
CRON_SECRET: any long random string (Vercel sends it to the cron route).
SUPABASE_SECRET_KEY: the project's secret key (Project Settings → API keys). Server-only.
RESEND_API_KEY and EMAIL_FROM (e.g. Aalto Football <hello@your-domain>): without them, nothing is sent and
reminders stay pending.
Analytics
Enable it once: Vercel → project → Analytics → Enable (Web Analytics, no cookies). The app already
includes the <Analytics /> script, which only loads when running on Vercel.
See it in the site:/admin shows visitors, page views, top pages, countries, referrers and devices for the
last 30 days when VERCEL_ANALYTICS_TOKEN, VERCEL_ANALYTICS_PROJECT_ID and VERCEL_ANALYTICS_TEAM_ID are set in
Vercel (token from vercel.com/account/tokens, stored as Sensitive). Without them, the panel links to the
Vercel dashboard. The community numbers (players, matches, fill rate…) come from Supabase and need nothing.
🚀 Deploy on Vercel
Root Directory:apps/web
Environment variables: none required; the public Supabase values are in apps/web/.env.production.
Set NEXT_PUBLIC_SITE_URL only if you use a custom domain.
🗺️ Roadmap
Landing page (English + Norwegian bokmål)
Installable PWA with offline page
Database schema, security rules and Bergen sample data
Sign in (password, email link, optional Google) and profile onboarding
Create, edit and cancel matches (hosts)
Match search with filters
Match page: join and leave, with waitlist
Share links, link-only private matches and calendar export
Email reminders before kick-off (needs Resend)
Map view of matches
Balanced teams, results, attendance, ratings and player profiles
Weekly matches, match chat and pitch admin
Password reset, admin panel with stats and analytics
Online payments (disabled for now)
🎨 Brand
Logo, colours, typography and tone (Spanish): docs/marca.md.
