Hi! We’ve been making a lot of changes lately, but one thing that’s stayed pretty much the same is the
fly launch command. As we’ve added more features to our platform, the UX of the launch command has gotten a little bit out of hand with its barrage of questions on the CLI. It’s not a great experience, especially if you’re just trying to learn how to use us.
The new launch provides nice sensible defaults, tailored to the app you’re launching (for example, if we detect a Rails app, we should default to Postgres unless the MySQL gem is present). Here’s the surprising part: naturally, you’re given the choice to change these defaults. If you do, we open a web browser.
The pile-o-forms we had for launch just isn’t working. In like 99% of cases, a CLI works great for interfacing with fly.io, but this was a bit of information overload, it was impossible to undo, and it’s just not easy to navigate. Instead, we give you a web page with nice inputs for everything, and then you can submit that to return to the CLI. It’s very slick, but far more importantly, it’s much easier to work with.
Don’t just take our word for it, though. It’s available right now, as
fly launch --ui! This is currently a preview phase - it’s not completely finished (it could use a final layer of UI polish, and provisioning databases & extensions isn’t 100% there yet), but we plan on replacing the existing launch with the new launch soon.
So, please try this out, and let us know if you have any comments or concerns!