Logbook - 2022-06-01

Here’s our latest changelog. Looking back over the week, our forum community has been quite a driver of (logged) change. When you’re done here, head over there to be a part of it! [Feature] Created an example Node.js app to demonstrate how to expo

Fly.io logo
Fly.io
•
The Fly.io Balloon
•4 min read•beginner•
--
•View Original
DockerGraphQLLaravelTerraform

Overview

The article provides a detailed changelog from Fly.io, highlighting new features, improvements, and fixes made to their platform. It emphasizes community contributions and offers insights into how developers can leverage these updates to enhance their applications.

What You'll Learn

1

How to expose multiple internal ports on separate public ports using a Node.js app

2

Why rolling restarts improve application availability during updates

3

How to utilize the official Terraform provider for Fly.io to orchestrate machines

4

When to use the fly status command to monitor VM failures effectively

Key Questions Answered

What new features were introduced in the Fly.io platform on June 1, 2022?
The article outlines several new features including a Node.js app example for multiple ports, a rolling restart feature, and an official Terraform provider for orchestrating machines. It also mentions improvements like increased visibility for failed VMs and enhancements to the web dashboard.
How can developers utilize the new Terraform provider for Fly.io?
Developers can use the official Terraform provider to manage Fly.io resources, ensuring feature parity with the Machines API. This allows for easier orchestration of applications and infrastructure, streamlining deployment processes.
What improvements were made to the Fly.io web dashboard?
Improvements to the Fly.io web dashboard include better readability for IP addresses and App Secrets, visibility of subscription discounts, and the ability to upgrade Livebook apps directly from the dashboard. These enhancements aim to improve user experience and accessibility.
What fixes were implemented in the Fly.io platform?
The article details various fixes including a bug on the certificates page, improved logging out functionality, and updates to the Tailwind classes for better visibility. These fixes enhance the overall reliability and usability of the platform.

Technologies & Tools

Some links below are affiliate links. We may earn a commission if you make a purchase.

Backend
Node.js
Used in the example app to demonstrate exposing multiple internal ports.
Infrastructure
Terraform
Used for orchestrating Fly.io resources and managing deployments.
API
Graphql
New endpoints were added to fetch volumes, IPs, and certificates.

Key Actionable Insights

1
Utilize the new rolling restart feature to minimize downtime during application updates.
This feature allows for seamless updates without taking the entire application offline, which is crucial for maintaining user experience and service availability.
2
Leverage the official Terraform provider to automate the orchestration of your Fly.io resources.
Using Terraform can significantly reduce manual configuration errors and streamline the deployment process, making it easier to manage infrastructure as code.
3
Engage with the Fly.io community forum to stay updated on best practices and troubleshooting.
The community is a valuable resource for learning from other developers' experiences and gaining insights into effective usage of Fly.io features.

Common Pitfalls

1
Failing to monitor VM statuses can lead to unnoticed application downtime.
Using the updated fly status command can help developers keep track of VM health and quickly address any issues that arise.