Going to Production

Prepare and deploy your application to production.

Here is a list of things you should have to proceed:

1. Database: A remote instance of your database. This can be self-hosted, or a managed provider (Supabase, Planetscale, Neon, Railway, etc.). You need a valid URL so you can push migrations to this instance.
2. Migrations: Once you have a remote database, you need to push your application's migrations to set up its schema.
3. Stripe and Billing: You need a set-up Stripe account, and you need to set up the Products and Prices with the correct Price IDs in the billing configuration.
4. Email: You need to set up a valid email provider (ex. SMTP, Resend, etc.) to be able to send out emails.
5. Storage: You need to set up a valid storage provider (ex. AWS S3, Cloudflare R2, etc.) to be able to store files.
6. OAuth (optional): if you use any OAuth provider, you must set up valid credentials (ex. Google, GitHub, etc.). If you don't use any, you can skip this step.

If you don't have all the information above - you may not be able to deploy your application to production, so it's best to go back and sort out the information before you proceed.

Production Checklist

Before deploying to production:

• ✅ Environment variables configured (see Environment Setup)
• ✅ Database migrations

Topics

1. Environment Setup - Production environment variables
2. Deployment - General deployment guidelines
3. Railway - Deploy to Railway
4. Docker - Deploy using Docker

Next: Deployment →