Deployment

This section explains deployment strategies and best practices for deploying your applications to production.

Deployment Options

Choose the deployment platform that best fits your needs:

Key Deployment Considerations

Database

Prepare your production database:

• Use a managed PostgreSQL service: Supabase, Neon, or AWS RDS
• Set DATABASE_URL in production environment variables
• Run migrations before deploying: pnpm db:migrate

Environment Variables

Set all required environment variables in your hosting platform.

The key variables needed for deployment are:

• DATABASE_URL - Production PostgreSQL connection
• BETTER_AUTH_SECRET - Authentication secret (must be identical across all services; see Environment Variables Guide)
• GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET - OAuth credentials
• RESEND_TOKEN - Email service API key
• UPSTASH_REDIS_REST_URL and token - Rate limiting

For detailed setup instructions and complete variable reference, see the Environment Variables Guide.

Security

Follow these best practices for production:

• HTTPS Only - Enable TLS/SSL encryption
• CORS - Restrict ALLOWED_ORIGINS to your domain only
• Secrets - Never commit .env files or API keys
• Updated Dependencies - Keep all packages up to date
• Health Checks - Monitor application health regularly

Preparation Checklist

Before deploying to production:

• Database migrated successfully
• All environment variables configured
• Build completes without errors: pnpm build
• Tests pass: pnpm test
• No TypeScript errors: pnpm check-types
• Linting passes: pnpm lint
• Google OAuth credentials verified
• Email service credentials set up
• Rate limiting (Redis) configured
• CORS origins whitelisted

Deployment Guides

• Vercel - Best for Next.js frontend and serverless API
• Docker - Self-hosted or any cloud provider