Hi! We’ve been reworking the
fly launch experience for a while.
It’s been in a public preview state for a little bit, but it finally got released to everyone as of
The main change here is how you specify what you want from your app.
In the old
fly launch, it would ask you a bunch of questions one-after-the-other, with no indication of how much more you’d have to configure. It’s a natural evolution of improvements and more features to the platform, but it’s gotten unwieldy. Even with all these questions, there are still a fair few cases where the app doesn’t work out of the box, which means there isn’t enough configuration!
Our primary solution to this is to come up with really good defaults. We’ll name the app after the parent directory, give you a good default machine, try to detect whether your app uses any of the databases we can run, etc. If we get it right, you just confirm that, and it’ll deploy everything. If not, you’re thrown into a web page that exposes the same configuration options from the launch you’re used to, and a little bit more.
Please note that as soon as you confirm your settings on the Launch UI, it’ll launch and deploy your application. If you don’t want to immediately deploy, you can pass
--no-deploy to the launch command.
If you’re running flyctl in an automated way, such as with CI, it should work just as it has before (aside from --reuse-app, which was removed). Any deviation from that is a bug, and we’d really appreciate a bug report so we could make that work for you. This is a complete rewrite of the launch command, so even with extensive testing, I expect there could be a couple things lurking around that don’t behave exactly as they did before.
We’re hoping this makes launching new apps on Fly easier and less error-prone. If you have any issues or feedback for this change, I’d love to hear it. Thanks!
There’s a slight bug in name generation that came from the chaos of getting all this merged. It doesn’t currently pull names from the working directory, and it lies about how it derived the app name it’s using. This will be fixed in