First Deployment

Generate and apply database migrations for production:

# Create migration from your schema changes
pnpm db:generate

# Review the generated migration file
cat prisma/migrations/[timestamp]_*/migration.sql

# Apply migrations to production database
pnpm db:migrate

Update your environment variables for production:

# Update these for production
NEXTAUTH_URL="https://yourdomain.com"
DATABASE_URL="postgresql://production-connection-string"

# Use production API keys
STRIPE_SECRET_KEY="sk_live_..."
NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY="pk_live_..."
RESEND_API_KEY="re_live_..."

Keep development keys in your local .env file. We'll configure production keys in Vercel's dashboard.

1. 1. Push to GitHub

   # Commit your changes
   git add .
   git commit -m "Ready for production deployment"
   git push origin main

2. 2. Connect to Vercel
   • • Go to vercel.com and sign in
   • • Click "New Project"
   • • Import your GitHub repository
   • • Vercel will auto-detect Next.js settings

Add your production environment variables in Vercel:

1. 1. In your Vercel project dashboard, go to Settings → Environment Variables
2. 2. Add each variable from your production .env file
3. 3. Set the environment to Production
4. 4. Click Save for each variable

Deploy your application:

1. 1. Click "Deploy" in Vercel
2. 2. Wait for the build to complete (~2-3 minutes)
3. 3. Vercel will provide your production URL
4. 4. Test your deployment

Update your external services with your production URL:

1https://yourdomain.com/api/auth/callback/google

1https://yourdomain.com/api/webhooks/stripe

Verify everything works in production:

Replace the Vercel URL with your custom domain:

1. 1. In Vercel project settings, go to Domains
2. 2. Add your domain (e.g., yoursaas.com)
3. 3. Configure DNS records with your domain provider:
   • • Add CNAME record pointing to Vercel
   • • Or follow Vercel's specific DNS instructions
4. 4. Update NEXTAUTH_URL environment variable
5. 5. Update OAuth and webhook URLs in external services