Rapid Deploy (Forge Dashboard)

Forge's frontend-app deploys to Vercel. Every push to main triggers a production deploy automatically. Every PR gets an isolated preview deployment.

Pre-Merge Checklist

Before merging any PR into main, confirm all of the following:

1. Build passes locally

npm run build

Expected: exits 0 with no TypeScript errors.

2. Environment variables are set in Vercel

Every key in .env.example must exist in Vercel project settings → Environment Variables → Production.

New env vars introduced in this PR must be added to Vercel before merging.

Keys to verify:

• NEXT_PUBLIC_BACKEND_URL
• NEXT_PUBLIC_DATA_URL

If a key is missing, add it in Vercel and re-deploy the preview before merging.

3. Preview URL tested

The Vercel bot posts a preview URL as a PR comment. Open it and verify:

• Login works end-to-end
• Dashboard loads and shows projects
• Project detail page opens and API keys display
• No errors in browser devtools Console

4. No debug artifacts in changed files

git diff main...HEAD -- '*.tsx' '*.ts' | grep '^\+.*console\.'

Remove any console.log / console.error in production code paths.

5. .env.example reflects all env vars

If this PR adds a new process.env.* reference, .env.example must be updated in the same PR.

Deploy

Merging to main triggers production deploy automatically. Watch it:

# Install Vercel CLI if needed: npm i -g vercel
vercel ls tessl-fe/frontend-app --prod

Or check the Vercel dashboard → Deployments tab. Expected build time: 60–90 seconds.

Rollback

If production is broken after a merge:

# List recent deployments
vercel ls

# Instant rollback — re-routes traffic to a previous build, no rebuild
vercel rollback <previous-deployment-url>

Common Build Failures

Build logs: open the deployment in Vercel dashboard → click "Build Logs".