Fly.io Application Release Lifecycle

Overview

Treat the app release as a state transition with explicit configuration, image, capacity, health, and rollback boundaries. Fly Launch manages Machines from fly.toml, but production success still requires reconciliation against the running fleet.

Prerequisites

• Source revision, image build contract, app name, environment, and primary region
• Reviewed fly.toml with process groups, services, health checks, and shutdown settings
• Approved deploy strategy, capacity envelope, secret plan, and rollback target

Instructions

Step 1: Inventory the current app

Record current release, running image, Machine counts and regions, health, IP allocation, secrets digests, and attached storage.

Step 2: Render the desired state