Logbook: October 21 to 28, 2022

Summary

This weekly Logbook changes format from tracking every monthly change to an over-generalized weekly tl;dr of Fly.io updates intended to help with deploying or managing apps. It reports new Postgres documentation for performing failovers, regional failovers, setting up and attaching a database, and migrating one from Heroku, while warning that Fly Postgres is not fully managed and requires customer monitoring. The post also points to an example of integrating the Elastic Stack (ELK) with a Laravel app for user analytics and reporting, plus instructions for shutting down an idle Phoenix app on Fly Machines after a configurable period without requests. It explains that newly launched Fly apps do not yet deploy to Machines in the same way, while fly pg create does use Fly Machines, and directs readers to comparisons of the app versions. Finally, it notes colorblind-friendly dashboard improvements and previews more Postgres documentation work.

Takeaways

1. 1

   New documentation covers performing Postgres failovers, regional failovers, setting up and attaching a database, and migrating a Postgres database from Heroku.

2. 2

   Fly Postgres is not a fully managed database: Fly provides tools to provision and upgrade instances, but an instance running out of disk space can go unnoticed without monitoring.

3. 3

   A Phoenix app can shut itself down on Fly Machines when it has received no requests for a configurable period of time.