Logbook - 2022-05-26

Work leading up to the Fly Machines launch involved a multitude of changes by many of the cogs in this corporate machine, but that’s not to say the other production lines have been idle. For one thing, our web UI has been transforming before our eyes

Fly.io logo
Fly.io
•
The Fly.io Balloon
•5 min read•intermediate•
--
•View Original
GraphQLPlanetScale

Overview

The article discusses the recent launch of the Fly Machines API, which allows users to start and stop fast-booting Firecracker VMs directly. It also highlights various updates and features in the Fly.io platform, including improvements to the web UI and new functionalities for Fly HA Postgres instances.

What You'll Learn

1

How to utilize the Fly Machines API for managing Firecracker VMs

2

Why monitoring volume usage in Fly HA Postgres is crucial for database health

3

When to implement proxy protocol v2 in your Fly.io applications

Key Questions Answered

What new features were introduced in the Fly Machines API?
The Fly Machines API allows users to directly start and stop fast-booting Firecracker VMs, providing a more efficient way to manage applications without orchestration. This API enhances the user experience by enabling quicker deployment of applications.
How does Fly HA Postgres handle volume fullness?
Fly HA Postgres instances will turn read-only and fail a health check when their volume reaches 90% capacity. This proactive measure helps users manage database growth and prevents crashes due to full disks.
What improvements were made to the web UI?
The web UI has undergone significant transformations, including a redesigned Apps dashboard, improved organization UI, and enhanced app pages for better user experience and access to information.
What changes were made to the GraphQL API error messages?
The GraphQL API now provides clearer error messages, specifically stating 'Could not find <some-app-name>' when an app cannot be located, instead of the previous vague message. This change improves troubleshooting for users.

Key Statistics & Figures

Volume capacity threshold for Fly HA Postgres
90%
Instances turn read-only and fail health checks when this threshold is reached, allowing users to react before a crash.

Technologies & Tools

Backend
Fly Machines
API for managing fast-booting Firecracker VMs.
Database
Fly Ha Postgres
Managed PostgreSQL instances with health check features.

Key Actionable Insights

1
Utilize the Fly Machines API to streamline your application deployment process.
By using the Fly Machines API, you can bypass orchestration and quickly start or stop Firecracker VMs, enhancing your application's responsiveness and deployment speed.
2
Monitor your Fly HA Postgres volume usage to avoid downtime.
With the new feature that turns instances read-only at 90% volume capacity, keeping an eye on your database's growth can prevent unexpected crashes and improve overall reliability.
3
Leverage the redesigned web UI for improved management of your Fly.io applications.
The new dashboard and app page designs provide better access to vital information and administrative tasks, making it easier to manage your applications effectively.

Common Pitfalls

1
Failing to monitor volume usage in Fly HA Postgres can lead to unexpected downtime.
When the volume reaches 90% capacity, instances become read-only, which can disrupt application functionality. Regular monitoring and proactive management of database growth are essential to avoid this issue.