Fly.io Local-to-Remote Development Loop

Overview

Keep local unit and container checks separate from provider integration checks. Use synthetic fixtures by default, validate configuration before deployment, and treat fly proxy or WireGuard access to a remote service as production-adjacent even when initiated from a laptop.

Prerequisites

• Local build and test commands plus expected runtime port
• Development-only app or isolated process group and disposable test data
• Approved remote-service access path with data handling and teardown rules

Instructions

Step 1: Define the parity contract

Record runtime image, architecture, process command, port, environment names, health route, filesystem expectations, and provider-only dependencies.

Step 2: Build and test locally