How razikus/supabase-nextjs-template works
Project type and purpose
• This is a full-stack SaaS template:
• Frontend built with Next.js 15 (App Router) + React 19 + Tailwind CSS + shadcn/ui
• Backend provided by Supabase (PostgreSQL, Auth, Storage, RLS)
• Demo features: authentication, file storage demo, task management demo, legal docs
File structure
• Top-level:
• nextjs/ → all Next.js code (pages, components, api routes, config)
• supabase/ → database migrations, config.toml, storage policies
• Patterns:
• Next.js App Router + serverless API routes under nextjs/src/app/api
• Client-side components under nextjs/src/app and nextjs/src/components
• Supabase client vs. serverAdmin client for browser vs. server calls
• Config and deployment:
• nextjs/.env.template → environment variables for Supabase URL/keys and theme
• supabase/config.toml → site_url, redirect URLs
• supabase migrations → SQL files for schema, RLS policies
Extract insights from the README
• Tech stack summary (Frontend, Backend, Auth)
• Features map: authentication flows, MFA, OAuth, file/task demos
• Deployment instructions: supabase CLI for migrations + Vercel for frontend
Architectural patterns & principles
• Client-Server separation: React UI vs. serverless API vs. BaaS
• App Router (Next.js 15) for nested layouts and route-based code splitting
• Edge vs. Server-only code: Supabase client in browser, serverAdminKeys on server
• Security via RLS and middleware guard in Next.js
• CI/CD pipeline: GitHub → supabase migrations & Vercel deploy