Flight World
A web app for logging and reviewing flights, built with Next.js, Supabase, and deployed on Vercel.
Stack
- Next.js (App Router, TypeScript, Tailwind CSS)
- Supabase for auth and data storage
- Vercel for hosting, deployed from this GitHub repo
Getting started
-
Install dependencies:
npm install
-
Create a Supabase project at supabase.com, then copy .env.local.example to .env.local and fill in your project's URL and anon key (Project Settings → API):
cp .env.local.example .env.local
-
Create the flights and user_preferences tables and their row-level security policies by running supabase/schema.sql in your project's SQL editor (Supabase dashboard → SQL Editor → New query). Already set up from an earlier version? Run supabase/migrations/20260926_ratings_and_favourites.sql instead — it adds the flights.rating column and the user_preferences table, and is safe to run more than once. Do this before deploying the ratings/favourites code, since the flights page selects the new column. Then run supabase/migrations/20261005_flight_details.sql, which adds the optional flight details (takeoff and landing times, landing rate, conditions, weather; its fuel columns are no longer used); until it's run the log still works, just without them (saving a flight with them says so). Then run supabase/migrations/20261006_sharing_and_confirmed_flights.sql, which adds share links and confirmed flights saved with the account (the flight_shares and confirmed_flights tables, with row-level security, and the shared_flight_map function that share pages read through); until it's run, the Stats page says sharing needs it and confirmed flights stay in the browser.
-
In the Supabase dashboard, under Authentication → URL Configuration, set the Site URL to http://localhost:3000 for local development (and add your Vercel domain once deployed). Email/password sign-up is enabled by default and requires confirming a link sent by email before a user can sign in.
-
Run the dev server:
npm run dev
Open http://localhost:3000.
Deploying
Import this repository in Vercel, add the same two environment variables from .env.local in the project's settings, and deploy. Every push to main will trigger a new deployment.
After deploying, add your Vercel URL (and any preview URLs) to Supabase's Authentication → URL Configuration → Redirect URLs so email confirmation links work in production.
Free-tier Supabase projects are paused after a period of inactivity. While paused, the auth API is unreachable and sign-in/sign-up fail with a "can't reach the sign-in service" message — restore the project from the Supabase dashboard (it takes a few minutes to come back up).
This is the beginning of the README. Read the rest at the original. Read the full README ↗
