How to deploy this project to different environments.
| Environment | URL | Branch | Auto-deploy |
|---|---|---|---|
| Production | https://app.example.com | main |
Yes/No |
| Staging | https://staging.example.com | develop |
Yes/No |
| Preview | PR-specific URLs | PR branches | Yes/No |
- Access to deployment platform (e.g., AWS, Vercel, Railway)
- Required credentials configured
- CI/CD pipeline set up
Describe what triggers automatic deployments.
main branch → Production
develop branch → Staging
Pull requests → Preview environments
# Deploy to staging
# [Add your command here]
# Deploy to production
# [Add your command here]| Variable | Description | Where to set |
|---|---|---|
DATABASE_URL |
Production database | Platform secrets |
API_KEY |
Production API key | Platform secrets |
Same as production, but with staging values.
- All tests pass
- Code reviewed and approved
- Database migrations ready (if any)
- Environment variables configured
- Feature flags set (if applicable)
# Check pending migrations
# [Add your command here]
# Run migrations
# [Add your command here]
# Rollback (if needed)
# [Add your command here]- Migrations run automatically before deployment: Yes/No
- Zero-downtime migration approach: Describe
# Rollback to previous deployment
# [Add your command here]- Identify the last known good version
- Rollback database migrations (if safe)
- Deploy previous version
- Verify functionality
- Endpoint:
/healthor/api/health - Expected response:
200 OK
# View production logs
# [Add your command here]
# View staging logs
# [Add your command here]Describe alerting setup (e.g., PagerDuty, Slack, email).
- Check CI/CD logs
- Verify environment variables
- Check for build errors
- Review recent changes
- Check application logs
- Verify database connectivity
- Check environment variables
- Verify dependencies installed
- Check monitoring dashboards
- Review recent changes for N+1 queries, memory leaks
- Consider rollback if critical