Skip to content

Fly deploy: always resume app after deploy (lifts post-crash suspension) #42

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dougdevitre merged 1 commit into from
May 16, 2026
Merged

Fly deploy: always resume app after deploy (lifts post-crash suspension) #42

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions .github/workflows/fly-deploy.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -195,6 +195,18 @@ jobs:
FLY_API_TOKEN: ${{ secrets.FLY_API_TOKEN }}
run: fly deploy --remote-only -a "$FLY_APP_NAME"

- name: Resume app if suspended
# A run of crash-restarts (e.g., bad env var) leaves the Fly
# app in a "Suspended" state at the edge — even a fresh
# healthy deploy can't lift it; the proxy returns 403 with
# x-deny-reason: host_not_allowed. Always issuing resume here
# is idempotent: if the app is already running, Fly returns
# success without side effects.
env:
FLY_API_TOKEN: ${{ secrets.FLY_API_TOKEN }}
run: |
fly apps resume "$FLY_APP_NAME" || true

- name: Print live URL
run: |
echo "::notice title=Live at::https://$FLY_APP_NAME.fly.dev"
Expand Down