| name | ops-deploy |
| description | Deploy the Your Project Rails application to staging or production. Supports local builds via bin/deploy-staging and CI/CD via branch pushes. |
| allowed-tools | ["Bash","Read"] |
Deploy Application
Deploy the Your Project Rails application to the specified environment.
Target environment: $ARGUMENTS (expected: staging or production)
Workflow
If target is staging
-
Choose deployment method:
- Local deploy (build and push from workstation):
bin/deploy-staging
- CI/CD deploy (push to staging branch): merge/push to
staging branch
-
For local deploy:
-
Post-deploy verification:
aws ecs describe-services \
--cluster webCluster \
--services web-rails-service worker-service \
--profile your-project-staging \
--region us-east-1 \
--query 'services[].{name:serviceName,running:runningCount,desired:desiredCount,rollout:deployments[0].rolloutState}' \
--output table
-
Check logs for errors after services stabilize:
aws logs describe-log-groups \
--profile your-project-staging \
--region us-east-1 \
--query 'logGroups[].logGroupName' \
--output table
Then tail the relevant log group for recent errors.
If target is production
-
Require explicit confirmation from the user before proceeding. Do NOT deploy to production without the user confirming they want to deploy.
-
Important: The production auto-deploy trigger (main branch) is currently commented out in .github/workflows/deploy.yml. Only the staging trigger is active.
-
CI/CD deploy: merge/push to main branch (if the trigger is re-enabled)
-
Post-deploy verification (same as staging but with --profile your-project-production)
Execution
Deploy now to the specified environment.
