We just released an App Deployments page that should give you some basic information about the GitHub repo attachment to your app, latest deployments and the coolest thing: deploy now button!
How does it work?
The deploy button pretty much reuses the entirety of our deployer image except now it asks zero questions, it just deploys your app! This is useful on cases such as you not having access to your console and wanting to ship something asap without any continuous deployment previously setup. Also this will be useful if you used our UI to stage secrets and just want to deploy.
Attaching repos
If you previously deployed an app via our Launch UI you could very well assume your repo was already attached to the app and that was true but we recently changed how we stored those attachments so we will need you to attach it once more. Apologies for the troubles of experimental features!
The one caveat
This page currently assumes your repo already has a fly.toml for an app you own. Later on we want to create more pathways you can take (what if you don’t own the app? what if you want to copy the config and launch the repo to this app?) but we just wanted to ship something that we feel could be useful even if the use cases are specific such as the one I described above
What’s next
Believe it or not, this is part of our work for continuous deployments. There’s many things to be addressed inbetween now and “we have built-in CD at fly.io” and, unless something else more important appears, we will be working on making the UX for newly launched apps to store their generated fly.toml (and other files such as Dockerfile, .dockerignore…). Spoiler alert: our UI will probably ask you if it can create a PR for you to add those files.
As usual we’d love any feedback! Did you love it? Does this feature sucks? Let us know
That would be great! I am using an NX monorepo, and I have 3 .toml files in different locations, and I expect that number to increase with time. I’d love to be able to still use the deploy UI after selecting the correct config file.
not an issue, just a weird problem if I would like to deploy and inner directory (not having this directory .gitignore, so it stops (i think, need logs).
Is this an alternative method to the github actions?
I have just created an app on Fly.io and at some point, some files were added in my repo, including a .github/workflows/fly-deploy.yml. I have also set up an automatic deployment from the dashboard.
Now when I push a commit on my main branch, the app is deployed (I think through the UI deployment) but github is also trying to deploy the app with an action (but fails, because I didn’t specify a secret token I think).
Should I understand there are two ways to automatically deploy a github repo, using github actions or the fly.io dashboard?
