Fly.io and Sprites

Inspect the app's fly.toml, Dockerfile, deployment workflow, and relevant runtime code before choosing changes. For Sprites, identify the organization, Sprite name, and CLI or SDK integration instead; Sprites uses sprite, not flyctl or fly.toml.

Use local command help and current official docs for commands, limits, pricing, and availability. Start with fly version and fly <command> --help, or sprite --help and its relevant subcommand help. A surviving CLI flag is not proof that a retired service is available. Do not install tools or create resources merely to inspect them.

Read the relevant reference