We’ve been pulling together some of the most common questions and setups we’ve seen in our Solutions Architecture sessions, where we help Fly.io users untangle infrastructure, get production-ready, or just make things suck less. Here is a selection of four new docs and guides inspired by those conversations: common problems, recurring setups, and stuff we wanted to share with a larger audience.
Building Infrastructure Automation Without Terraform
Not every app needs a heavyweight provisioning tool. This guide shows two flexible options for automating your infrastructure setup.
App Suspend/Resume Reference
You can suspend apps and resume them later, with volumes, IPs, and config intact. It’s great for staging, quiet hours, or anything you don’t want to keep burning resources. This doc walks through tradeoffs, exactly what’s preserved and what isn’t, and what to watch out for.
Rolling Back App Deploys
Deployed something that broke? Here’s how to quickly roll back, plus tips on what to check before and after to make sure you don’t end up here again.
Getting Started with N-Tier Architecture on Fly.io
How to structure an app as separate Fly.io services connected on the same private network. It’s the clean, low-overhead foundation most reliable web apps are built on.
We continue creating and updating docs based on what folks are doing in the wild. If you find something confusing or you hit a wall, let us know here or file a GitHub issue.
Check back soon for more new docs and guides!