⚡ Fullstack Starter

Production-ready fullstack starter — React + NestJS + Supabase + PostgreSQL + Auth + CRUD. TypeScript everywhere.

---

🚀 Getting Started

# 1. Clone the repo
git clone https://github.com/guyboireau/fullstack-starter.git && cd fullstack-starter

# 2. Install all dependencies
npm install

# 3. Configure environment variables
cp .env.example .env   # Then fill in your Supabase credentials

# 4. Start the dev servers
npm run dev

Frontend → http://localhost:5173  |  API → http://localhost:3000

---

🏗️ Architecture

fullstack-starter/
├── apps/
│   ├── web/          → React 19 + Vite 6 + React Router 7
│   └── api/          → NestJS 11 (REST API)
├── supabase/
│   ├── migrations/   → SQL migrations (profiles, items)
│   └── seed.sql      → Sample data
├── docker-compose.yml
└── .github/workflows/ci.yml

How it works: The React frontend authenticates users via Supabase Auth (email/password). Authenticated requests hit the NestJS API, which validates JWTs using a custom SupabaseAuthGuard. All database operations go through Supabase's client library with Row Level Security (RLS) — each user can only access their own data. The API uses a user-scoped Supabase client that respects RLS policies automatically.

---

✨ Features

Feature	Details
🔐 Authentication	Login, Register, Logout via Supabase Auth
📝 CRUD	Full Create, Read, Update, Delete on Items
🛡️ Auth Guard	NestJS guard validates Supabase JWTs
🔒 Row Level Security	PostgreSQL RLS — users only see their own data
🎨 Modern UI	Dark mode, glassmorphism, gradient accents
📊 Dashboard	Stats overview + item management
✅ Validation	DTOs with class-validator on the API
🐳 Docker Compose	One-command local dev environment
🔄 CI/CD	GitHub Actions: lint + typecheck on every PR
📦 Monorepo	npm workspaces — single npm install

---

🗄️ Database Schema

profiles

Column	Type	Description
id	UUID (PK)	References auth.users
email	TEXT	User email
full_name	TEXT	Display name
avatar_url	TEXT	Profile picture URL
created_at	TIMESTAMPTZ	Auto-set

items

Column	Type	Description
id	UUID (PK)	Auto-generated
user_id	UUID (FK)	Owner reference
title	TEXT	Item title
description	TEXT	Optional details
status	TEXT	todo | in_progress | done
created_at	TIMESTAMPTZ	Auto-set

---

🔑 API Endpoints

All endpoints under auth require a Bearer token in the Authorization header.

Method	Endpoint	Auth	Description
GET	/auth/profile	✅	Current user profile
GET	/users/me	✅	User profile from DB
GET	/items	✅	List all items
GET	/items/:id	✅	Get single item
POST	/items	✅	Create item
PATCH	/items/:id	✅	Update item
DELETE	/items/:id	✅	Delete item

---

☁️ Deploy

Frontend → Vercel

1. Import the apps/web directory on Vercel
2. Set the Root Directory to apps/web
3. Add environment variables: VITE_SUPABASE_URL, VITE_SUPABASE_ANON_KEY
4. Deploy 🚀

Backend → Railway / Render

1. Create a new service on Railway or Render
2. Set the Root Directory to apps/api
3. Build command: npm run build
4. Start command: node dist/main
5. Add environment variables from .env.example

---

🧰 Supabase Setup

1. Create a new project at app.supabase.com
2. Go to SQL Editor and run the migration files in order:
   • supabase/migrations/00001_create_profiles.sql
   • supabase/migrations/00002_create_items.sql
3. Copy your project URL + anon key from Settings → API
4. Paste them in your .env file

---

🐳 Docker (optional)

# Start all services (PostgreSQL + API + Web)
docker compose up -d

# View logs
docker compose logs -f

# Stop everything
docker compose down

---

🏆 Built with this stack

This isn't a tutorial copy-paste — it's the production stack I use for real client projects:

• Niido — Rental management platform
• La Lucarne — Real estate agency
• Les Cours de Clara — Online tutoring platform

---

📄 License

MIT — use it, fork it, build with it.