Fly.io Runtime and Platform Change Control

Overview

Replace the obsolete Apps v1-to-v2 tutorial with ongoing change control for the current Machines platform. Treat flyctl, fly.toml, images, architecture, Machine resources, regions, volumes, and Managed Postgres as separate migration surfaces with distinct rollback and data risks.

Prerequisites

• Current and target versions, configuration, image, architecture, resources, regions, and data topology
• Provider documentation and release notes retrieved at the change boundary
• Backup, export, restore test, acceptance gates, owner, approver, and rollback window

Instructions

Step 1: Classify the change surface

Separate CLI behavior, config schema, API contract, image or runtime, CPU architecture, VM size, region placement, volume state, and Managed Postgres changes.

Step 2: Freeze current state and contract