Skip to content

Fly deploy: install flyctl manually so PATH propagates to next step #38

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
+10 −1
Merged

Fly deploy: install flyctl manually so PATH propagates to next step #38

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
11 changes: 10 additions & 1 deletion .github/workflows/fly-deploy.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,7 +108,16 @@ jobs:
echo "wrote $(wc -l < $RUNNER_TEMP/secrets.env) entries"

- name: Setup flyctl
uses: superfly/flyctl-actions/setup-flyctl@master
# superfly/flyctl-actions/setup-flyctl@master left flyctl off
# the runner PATH for the next step (cmd-not-found, exit 127).
# Install manually + append to GITHUB_PATH so every subsequent
# step sees the binary.
run: |
curl -L https://fly.io/install.sh | sh
echo "$HOME/.fly/bin" >> "$GITHUB_PATH"
# Verify in this same step (uses absolute path because the
# PATH change only takes effect for later steps).
"$HOME/.fly/bin/flyctl" version

- name: Ensure Fly app exists
env:
Expand Down