Food Rescue Network

Next.js App Router platform for routing leftover food from donors to nearby NGOs with realtime tracking and milestone confirmations.

Implemented flows

• Role-based auth (DONOR, NGO, VOLUNTEER) with next-auth credentials provider
• Donor donation reporting with map pin selection
• Top-3 nearest NGO matching using distance-based ranking
• NGO inbox accept/decline workflow (first acceptance wins)
• End-to-end delivery lifecycle tracking
• Shared donor/NGO tracking page with map + immutable timeline
• Volunteer dispatch with expiring offers and automatic reassignment
• Donor pickup OTP, volunteer GPS ingestion, and geofence arrival automation
• In-app notifications with per-user deletion
• Ably realtime updates with database-backed retry delivery

Tech stack

• Next.js 16 (App Router)
• React 19
• Prisma + Vercel Postgres (Neon)
• Auth.js (next-auth)
• shadcn/ui components (installed via npx)
• MapLibre GL + OpenStreetMap
• Ably Pub/Sub
• Toast-based confirmation UX (no external email provider)

Environment

Copy .env.example to .env and set values:

cp .env.example .env

Required:

• POSTGRES_PRISMA_URL
• POSTGRES_URL_NON_POOLING
• NEXTAUTH_URL
• NEXTAUTH_SECRET
• PICKUP_OTP_SECRET
• ABLY_API_KEY (server-only; never use a NEXT_PUBLIC_ prefix)

Optional fallback:

• DATABASE_URL (for local/non-Vercel databases)

Development

Install dependencies and run:

npm install
npm run db:generate
npm run dev

There is no separate worker. After each authenticated API request, the server expires stale volunteer offers, reassigns them, and publishes pending Ably events (lib/background-sync.ts).

Database migrations

npm run db:migrate

For production:

npm run db:deploy

Deploy on Vercel

1. Import this repository in Vercel.
2. Add environment variables from .env.example in the Vercel project settings:
   • POSTGRES_PRISMA_URL
   • POSTGRES_URL_NON_POOLING
   • DATABASE_URL (optional fallback)
   • NEXTAUTH_URL (set this to your production domain)
   • NEXTAUTH_SECRET
   • PICKUP_OTP_SECRET
   • ABLY_API_KEY
3. Keep the Vercel build command as default (npm run build).
4. Run migrations before first production traffic:

npm run db:deploy

If you want a single command that includes migrations + build in non-Vercel environments, run:

npm run build:prod

Build checks

npm run lint
npm run build