fly-deployment

What problem does it solve?

This skill helps teams deploy applications to Fly.io by addressing the one-volume-per-machine limitation, monorepo deployment patterns, and practical Dockerfile guidance.

Core Features & Use Cases

• Monorepo deployment guidance: place fly.toml at project root and configure per-app deployments, with examples like apps/api and apps/web.
• Volume management: design deployments with a single volume and subdirectories to avoid multiple mounts.
• Dockerfile patterns: guidance for Next.js and Python apps, multi-stage builds, and per-app dockerfile organization.
• Troubleshooting: actionable steps for common issues including Next.js context errors, Dockerfile path mistakes, and TLS proxy considerations.

Quick Start

Create root fly.toml files for each app and run fly deploy --config fly.api.toml and fly deploy --config fly.web.toml from the project root. Ensure Dockerfiles exist at the specified paths (e.g., apps/api/Dockerfile, apps/web/Dockerfile) and that per-app configs reference the correct dockerfile paths.