Fly.io apps can now auto-deploy when you push your code to GitHub when you’ve connected the app using our new Launch UI
Our new Launch UI is still very much in progress but we wanted to share this exciting new development with you.
You can now skip a bunch of steps and have us auto-deploy your apps for you when you push to your GitHub repository.
Set it up
Navigate to your App > Deployments and select “settings.” From there you can enable auto-deploying and specify which branch we should be watching to deploy.
If you haven’t setup GitHub deployments for your app yet (they’re new), you may have to walk through some of our Launch setup on the Deployments page before you can enable this setting.
What’s next
This work takes some of the basics of Deployment from our new Launch UI and attaches that to GitHub’s integration points.
There are a ton of exciting ways to better integrate these GitHub with Fly.io apps and make it easier to more directly and obviously connect code changes in GitHub to deployments on your apps.
More immediate than those exciting connection points between us and GitHub, we need to bring you better ways to inspect these Deployments to understand what happened, when it failed. This is a bit different now that these deployments happen out-of-band from your UI session but it’s an important piece of making these deployments useful. Stay tuned.
I’ve enabled it, but it doesn’t seem to actually work. It’s pretty unclear if it actually works.
Also, it would be nice to have the build log and the current stage (started, deploying, canceled).
Honestly, not a ton yet. For folks that are setting up their apps through the new Launch UI it’s just meant to be a bit easier to flip on. If GitHub Actions is working for you right now that’s great. That answer may change as get better answers to things like the question above.
The downside of deploying via GitHub Actions is that the build times are longer and the more builds you have, the more the billing meter rotates that you didn’t really need in GitHub Actions compared to this integrated feature.
the more builds you have, the more the billing meter rotates that you didn’t really need in GitHub Actions compared to this integrated feature.
Aren’t you just moving build costs from your Github Actions machine to your Fly app builder machine? So I’m not quite getting the billing meter argument. Is Fly is subsidizing build costs? And lets say yes, can we really count on that lasting forever?
If you haven’t setup GitHub deployments for your app yet (they’re new), you may have to walk through some of our Launch setup on the Deployments page before you can enable this setting.