Launching to Victory

Summary

Fly.io introduces a streamlined version of its fly launch command for deploying applications near their users. The CLI now infers desired infrastructure from application source code and offers opinionated defaults or alternative options when it cannot apply the same shape. Previously, the launch flow asked a series of questions; the change reduces guesswork by folding varied frameworks, languages, and toolchains into a few basic infrastructure shapes. A Rails application using SQLite is given an example set of defaults that developers can build from, while other applications can be configured through a confirmation webpage. Once settings are accepted, the app is built and deployed unless --no-deploy is supplied, and the CLI provides a link to the running app.

Takeaways

1. 1

   fly launch infers application infrastructure from source code instead of relying entirely on a sequence of questions.

2. 2

   Rails applications using SQLite receive an opinionated set of defaults, while other applications can be configured through alternative options.

3. 3

   After confirmation, the application is built and deployed automatically unless --no-deploy is used; the CLI then provides an app link.