Check commands
Keep the project commands: install through vercel-install and build through vercel-build if they already stabilized deployment.
- Install Command: bash scripts/vercel-install.sh
- Build Command: bash scripts/vercel-build.sh
- Node.js: 20.x
Deploy tower
Vercel setup
What to check in Vercel before redeploy: variables, build commands, domain, logs, and cache mode.
Redeploy is not a dice roll. It needs a checklist before the button is pressed.
Check variables
Vercel should hold all production variables for Supabase, Stripe, OpenAI, Resend, security tokens, and site URL.
- NEXT_PUBLIC_SITE_URL=https://www.omenhall.com
- Stripe keys are not test keys when real money is enabled.
- EMAIL_FROM matches a verified domain once ready.
Redeploy without stale cache
If strange errors persist after uploading the archive, redeploy without existing build cache.
- Use existing Build Cache: No for suspicious errors.
- Check Build Logs and Runtime Logs separately.
- Visit production after Ready.
checklist
What to check
- All env vars are set in the correct environment: Production, Preview, Development.
- Old keys are removed or rotated.
- Domain and www settings point to one canonical host.
- Build Logs do not contain secrets.
red flags
When to stop
- Vercel shows Ready, but functions fail in Runtime Logs.
- Production uses a test webhook or vice versa.
- Site loads with wrong brand or stale cache.
done when
Definition of done
- Production deployment is Ready and main pages open.
- Runtime Logs are clean after manual test.
- Variables are not exposed in the repository.
related doors