| name | deploy-production |
| description | Standardized deployment workflow for this specific project's infrastructure. Prevents deployment failures from skipped steps or wrong order. [GENERATED BY MOTIF — review and customize] |
Deploy Production
Standardized deployment workflow for this specific project's infrastructure. Prevents deployment failures from skipped steps or wrong order.
When to Use
- User says 'deploy', 'push to production', or 'ship it'
- After a session-wrapup when deployment is requested
- Don't skip when: even if 'nothing changed' -- verify deployment state
Instructions
- cd to project root directory
- Ensure all changes are committed and pushed to remote
- Deploy server to Fly.io:
fly deploy --local-only
- Deploy client from client/ subdirectory to Vercel:
cd client && vercel --prod
- Verify both deployments succeeded by checking output
- If either deployment fails, read error output and troubleshoot before retrying
Best Practices
- Always commit and push before deploying
- Deploy server before client to avoid version mismatches
- Check deployment logs for warnings even if deploy 'succeeds'
Common Pitfalls
| Problem | Solution |
|---|
| Deploying from wrong directory | Always cd to project root first |
| Forgetting the --local-only flag for Fly.io | Always use --local-only to avoid remote builder issues |
Key Constraints
- Always deploy from project root
- Use --local-only flag for Fly.io deployments
- Deploy server before client
