Deploy to Vercel
The Next.js web dashboard (apps/web) is optimised for deployment on Vercel.
Prerequisites​
- A Vercel account.
- A Supabase Cloud project with the schema initialised.
- Your production domain (optional but recommended).
Steps​
1. Import the Repository​
- Log into Vercel and click "Add New Project".
- Import your fork of
MAX-786/project-nexusfrom GitHub. - Vercel will auto-detect the TurboRepo monorepo structure.
2. Configure Build Settings​
Vercel should auto-configure these, but verify:
| Setting | Value |
|---|---|
| Framework Preset | Next.js |
| Root Directory | ./ (leave as root) |
| Build Command | turbo run build --filter=web |
| Output Directory | apps/web/.next |
3. Set Environment Variables​
In the Vercel project settings, add these environment variables:
| Variable | Description |
|---|---|
NEXT_PUBLIC_SUPABASE_URL | Your Supabase project URL. |
NEXT_PUBLIC_SUPABASE_ANON_KEY | Your Supabase anonymous (public) key. |
NEXT_PUBLIC_SITE_URL | Your Vercel production domain (e.g., https://nexus.yourdomain.com). |
4. Deploy​
Click "Deploy". Vercel runs the TurboRepo build and deploys the Next.js app.
Continuous Deployment​
Vercel automatically triggers a new deployment on every push to your main branch. Preview deployments are created for pull requests.
Post-Deployment: Update Supabase Auth Settings​
After deploying, update your Supabase project's auth settings:
- Go to Supabase Dashboard → Auth → URL Configuration.
- Set Site URL to your Vercel production domain.
- Add your Vercel domain to the Redirect URLs list.
This ensures auth redirects work correctly in production.
Extension Deployment (Chrome Web Store)​
To publish the extension:
cd apps/extension
pnpm build
This generates a production build in apps/extension/build/chrome-mv3-prod/. Upload the folder (or zip it first) to the Chrome Developer Dashboard.