Deploy to Vercel
1
Push code to GitHub
Ensure your latest changes are committed and pushed to the
main branch.2
Import in Vercel
Go to vercel.com, click Import Project, and select your repository.
3
Configure environment variables
In Vercel dashboard → Settings → Environment Variables, add:
4
Deploy
Vercel auto-deploys on every push to
main. Check build logs for errors.Production Checklist
Critical Variables
BETTER_AUTH_URL— Must match your actual production domain. Wrong values cause broken email verification and password reset links.MONGODB_URI— Must include/SignalisticsDB?in the connection string. See Environment Variables.BETTER_AUTH_SECRET— Use a strong, unique secret different from development.
Email Configuration
NODEMAILER_EMAIL— Gmail account for sending emailsNODEMAILER_PASSWORD— Gmail app password (not your regular password)- Test email delivery after deploying
Post-Deploy Verification
- Auth Flow
- Database
- Sign up with a new account
- Verify the email is received with correct production URLs
- Click the verification link
- Sign in with the verified account
- Test password reset flow
Monitoring
After deployment, keep an eye on:- Email delivery success rate
- Authentication errors in Vercel logs
- Database connection stability
- API rate limits (Finnhub, Gemini)
Rollback Plan
If issues occur after deployment:- Keep previous environment variable values documented
- Have a database backup ready
- Revert
BETTER_AUTH_URLif email links break - Use Vercel’s instant rollback to a previous deployment