This is the Fly Changelog where we list all significant changes to the Fly platform, tooling and web sites. You can also use the RSS feed of just changelog posts available on fly.io/changelog.xml or consult our dedicated ChangeLog page with all the recent updates.
Since the last ChangeLog, we’ve introduced some enhancements to
flyctl which make it easier to deploy tagged local and remote images directly to Fly. There is also a new load-balancing algorithm in operation which should be more effective with widely deployed global applications.
30th April 2020
flyctl: Version 0.0.117 released
flyctl auth dockercommand. This allows users to deploy images directly to fly by adding
registry.fly.ioto the docker daemon’s authenticated registries. (Resolves #104)
flyctl deployenabling a specific image label to be requested at deployment time. (Resolves #110)
- Timeout increased at end of deployment monitoring to stop erroneous
No Deploymentmessages. (Fixes #113)
flyctl deployversion negotiation to resolve API compatibility errors. (Fixes #112)
- Added a new Open Source page which covers details of how Fly works, and will be working, with open source projects.
- A new load balancing allocation algorithm is in place. Designed for global applications with large numbers of instances, an incoming connection will be directed to an instance from the closest least loaded service in a set of three services. Those three services will have been randomly selected from healthy services in the three nearest regions for the app.