May 2020 Summaries

The Fly Changelog has announced significant updates to the Fly platform, tooling and web sites. Pause/resume functionality is now available for applications, allowing users to pause (remove all running instances) and resume (start up one running instance) of an application. Additionally, a quicker way to view your Fly apps has been introduced. The changelog can be accessed through the blog or an RSS feed at fly.io/changelog.xml. There are also updates to the Deno Buildpack, which now supports unstable Deno builds when .unstable is added to the application directory. A new flyctl open command has been released, allowing users to look up the currently deployed application's hostname and instruct a web browser to open that URL.

The latest feature of Fly is now available - the ability to pause applications, which saves their state and reduces running instances to zero while maintaining networking configuration, IP addresses, and certificates. This can be useful for mothballing projects or managing costs. When ready to resume, flyctl resume brings back one instance at a time, allowing users to scale up as needed with the flyctl scale set min=n command. The regions command has also been enhanced with a set command for easier region pool management. Additionally, flyctl now displays an application's current status and includes a new open command that opens the user's web browser to the application's hostname after deployment.

The text discusses how to use WebSocket connections with the platform "Fly". It provides an example of a chat application that uses raw WebSockets (flychat-ws in fly-examples) and explains how to deploy it on Fly. The source code for this application is also examined, including the configuration file fly.toml and server.js file. Additionally, the client-side JavaScript code responsible for handling WebSocket connections is analyzed. Finally, the text highlights some of the benefits of using Fly, such as its ease of deployment, TLS connection management, and global infrastructure support.

Wocket is a proof-of-concept application that demonstrates how to stream live video from your browser to an RTMP server. It uses Next.js and a custom server with WebSockets. The project aims to showcase the possibility of streaming without using traditional encoder software like OBS or Ecamm Live. Wocket utilizes Mux's live streaming API, which provides an on-demand RTMP server for streaming purposes. To run the application locally, users need to install ffmpeg and have it in their $PATH. The project is a fun proof-of-concept and not intended for production use.

The Fly Changelog is a record of significant updates to the Fly platform, tooling, and websites. Notable changes since the last update include a new scaling system with updates to flyctl, improved performance of backhaul traffic movement between edge and datacenters, and the removal of references to 32-bit versions of flyctl for Windows and Linux. Additionally, there have been releases of flyctl version 0.0.122, which includes a new scaling mechanism and removed the autoscale command; flyctl version 0.0.121, with added autoscale and regions commands; flyctl version 0.0.120, with consistent naming for binary artifacts; and flyctl version 0.0.118, which fixes custom Dockerfile mapping issues.

Dj Walker-Morgan has announced that Deno, a secure runtime for JavaScript and TypeScript, has reached version 1.0. The author explains how to deploy Deno applications onto Fly, allowing them to run closer to users. They discuss the benefits of using a Dockerfile for deployment, which provides complete control over packaging and can lead to smaller image files and better build time performance compared to using a buildpack. The article then walks through building and deploying Deno with a Dockerfile, including creating a Dockerfile, exposing ports, copying dependencies, running the application, and testing locally. Finally, it demonstrates how to deploy the application to Fly using flyctl init and flyctl deploy commands.

Fly has introduced a new scaling model and commands to improve the user experience. The previous system was rigid and required manual resetting of regions. The new system is based on a pool of regions, allowing for more automation and management of global load. Two scaling models are available: Standard and Balanced. Additionally, new flyctl commands have been added for managing regions and scaling settings.

The Fly Changelog lists significant updates to the Fly platform, tooling, and websites. Recent changes include enhancements to flyctl, which now allows direct deployment of tagged local and remote images to Fly. Additionally, a new load-balancing algorithm has been implemented for global applications with large numbers of instances. On April 30th, 2020, flyctl version 0.0.117 was released, introducing the auth docker command, enabling image label requests at deployment time, and resolving API compatibility errors. A new Open Source page has also been added to provide information on how Fly works with open source projects.