Fly Changelog for 9th June

Summary

The 9th June Fly Changelog describes updates to flyctl, Fly platform tooling, and related web sites, centered on installation, application management, monitoring, and Deno builds. New installation instructions support macOS and Linux through a shell script, while a PowerShell command provides native Windows installation and flyctl now installs under $HOME/.fly/bin or configured $FLYCTL_INSTALL/bin. New commands let users restart applications, list accessible apps and organizations with text, organization, and status filters, or resume deployment monitoring with flyctl monitor. The open command accepts a URL path, secret updates automatically start monitoring for redeployment, and upgrade messages move to stderr for CI tooling. The Deno Buildpack now reads configuration from a required .config file, which also allows selecting the Deno version; an empty file is valid, while its absence produces an explanatory error.

Takeaways

1. 1

   flyctl now installs to $HOME/.fly/bin by default, or to $FLYCTL_INSTALL/bin when that variable is set; native Windows installation is supported through a PowerShell command.

2. 2

   flyctl apps restart, flyctl list apps, flyctl list orgs, and flyctl monitor add application restart, filtered app and organization listing, and persistent deployment monitoring.

3. 3

   The Deno Buildpack requires configuration in .config, including selectable Deno versions; an empty file is valid, but omitting it produces an error explaining how to create one.