April 2020 Summaries

Fly, a platform for building, deploying, and scaling applications, has introduced support for Deno, a secure runtime for JavaScript and TypeScript. The integration makes it simple to configure, build, and deploy Deno code with just two commands. Fly's builder support is based on Cloud Native Buildpacks specifications and implementations, which provide a repeatable build process for different languages and frameworks. This streamlined process allows developers to quickly create and deploy Deno applications on the Fly platform.

Fly has introduced a one-click launcher for Imaginary, an open source project that provides global image services using Imaginary. This new feature aims to simplify the process of converting, resizing and other image manipulation tasks. The creators of Imaginary have also added this one-click launcher to their README on GitHub. Fly is looking for more open source projects to collaborate with in order to create a valuable way for these projects to fund themselves through revenue sharing. Interested project owners can contact Christina, Fly's Community Manager, for more information.

The Fly Changelog has been updated with significant changes to the Fly platform, tooling and web sites. This includes earlier certificate renewals for infrastructure, a dedicated ChangeLog page, user contributed changes to flyctl for easier debugging of fly.toml files, better help for scaling VM sizes, and flyctl being packaged for Arch Linux. Additionally, new applications now get their app.fly.dev certificate instantly, and the Fly Proxy will serve new certificates two weeks before the current one expires if possible. A new ChangeLog page has also been added to bring together all recent changelogs into one readable page.

The Fly Changelog is a record of significant updates to the Fly platform, tooling, and websites. On April 7th, FlyCtl v0.0.115 was released with Buildkit support and an option for async parallel builds. Additionally, the --squash option for deploy was removed. The Fly Platform/Web also received improvements such as code samples in documentation having a copy icon for easier pasting. On April 3rd, FlyCtl v0.0.114 added --build-args support to pass build arguments to the build process. Lastly, on April 2nd, changelog capturing began and support was added for USER <uid> and USER <uid>:<gid> in docker files with numeric values. TLS handshake performance was improved, and reaping of zombie processes was integrated.

The text discusses deploying Docker images to Fly infrastructure using flyctl. It explains how to identify your build with flags like --config and --dockerfile, and control the build process with options such as ARG and ENV in a Dockerfile. Additionally, it introduces the use of --build-args for passing non-sensitive data during the build process. The text also highlights that sensitive information should not be passed using --build-args but rather through Fly Secrets for secure storage and injection into the application when running on the Fly platform.

The text discusses various aspects of using Fly, a platform for deploying applications. It covers how users can ask questions about Fly and where they can find answers. Additionally, it addresses concerns regarding malicious TCP connections and potential charges incurred due to such attacks. Furthermore, the text provides guidance on creating dedicated deploy keys for GitHub Actions CD workflows using Fly and mentions a new option --dockerfile for the flyctl deploy command that allows users to specify which Dockerfile should be used in the build process.