Deployment
Before deploying, run:
Fix build errors before shipping.
Do not deploy with placeholder billing URLs, test API keys, or old metadata images. Buyers will see those in production.
Environment Variables
Add the same production values to your hosting provider that you use locally.
Common variables:
Only expose variables with NEXT_PUBLIC_ when the browser needs them.
Vercel
Recommended for most users.
- Push the project to GitHub, GitLab, or Bitbucket.
- Import the project in Vercel.
- Confirm framework is Next.js.
- Add environment variables.
- Deploy.
Vercel settings:
Railway
- Create a new Railway project.
- Deploy from GitHub.
- Add environment variables.
- Generate or connect a domain.
Render
Use:
Add environment variables in Render dashboard.
VPS
Install dependencies:
Build:
Start:
For production VPS deployments, use PM2 and Nginx.
Example:
Example Nginx reverse proxy:
Use your own SSL setup, such as Certbot or your hosting provider’s certificate manager.
Post-Deploy Tests
After deployment, open production pages directly:
Then test:
- Checkout links.
- Domain lookup.
- Status API.
- Game stock API.
- Discord widget.
- Metadata preview.
- Mobile layout.
Production Checklist
- Environment variables are set.
- Billing URLs are production URLs.
- Brand assets are replaced.
- SEO metadata is updated.
- Product data is accurate.
- Light and dark mode are readable.
- Domain lookup works.
- Status page works.
- Game stock works if enabled.
- License file is included.
- Build succeeds.