deploy-shot-elixir
Deploy the shot-elixir Elixir/Phoenix application to Fly.io. Use this skill when deploying backend changes, updating environment variables, or releasing new versions to production.
When & Why to Use This Skill
This Claude skill automates the deployment process for Elixir/Phoenix applications to Fly.io. It streamlines backend updates, environment variable management, and production releases, ensuring a consistent and reliable delivery pipeline with built-in health checks and monitoring.
Use Cases
- Production Releases: Deploying the latest backend changes and new features to the live Fly.io environment with a single command.
- Environment Configuration: Updating and managing environment variables and secrets to ensure the production backend is correctly configured.
- Post-Deployment Verification: Automatically monitoring deployment logs and testing critical API endpoints (e.g., health checks, auth) to confirm system stability.
- Troubleshooting and Rollbacks: Rapidly identifying deployment failures through log analysis and executing rollbacks to maintain high availability.
| name | deploy-shot-elixir |
|---|---|
| description | Deploy the shot-elixir Elixir/Phoenix application to Fly.io. Use this skill when deploying backend changes, updating environment variables, or releasing new versions to production. |
Deploy shot-elixir to Fly.io
Instructions
- Navigate to the shot-elixir directory
- Verify all changes are committed to git
- Check that tests are passing (optional but recommended)
- Execute the deployment using
fly deploy - Monitor the deployment logs for errors
- Verify the application is running on https://shot-elixir.fly.dev/
- Test critical API endpoints after deployment
Deployment Steps
# Navigate to shot-elixir
cd /Users/isaacpriestley/tech/isaacpriestley/chi-war/shot-elixir
# Verify git status
git status
# Deploy to Fly.io
fly deploy
# Monitor deployment
fly logs
# Verify health
curl https://shot-elixir.fly.dev/api/v2/health
Examples
- User: "Deploy the latest changes to shot-elixir"
- User: "Release shot-elixir to production"
- User: "Push the backend changes to Fly.io"
- User: "Deploy elixir"
- User: "Update the production backend"
Guidelines
- Always verify commits before deploying
- Check that environment variables are properly set on Fly.io
- Monitor deployment logs for errors
- Test critical endpoints after deployment (auth, campaigns, characters)
- Update documentation if configuration changes
- Deployment typically takes 2-3 minutes
Post-Deployment Checks
- Test user authentication
- Verify WebSocket connections work
- Check database migrations applied successfully
- Test AI image generation endpoints
- Verify ActionCable/Phoenix Channels connectivity
Troubleshooting
If deployment fails:
- Check
fly logsfor error messages - Verify database connection with
fly ssh console - Check environment variables with
fly secrets list - Review recent git commits for breaking changes
- Rollback if needed:
fly releases rollback