Take a stack that already works under `flisk up` to Fly.io with that host's own tooling - `fly.toml` per service, `fly secrets set`, `fly deploy`. It maps each service.json (ports, health checks, dependencies, env) to production artifacts written for the host, never the local `.autogenerated/` files. Use when the user wants to ship a working Flisk stack to Fly.io. Flisk itself stays local; for Helm, Argo CD or Kustomize pipelines use flisk-helm.
Installs into .claude/skills of the current project.
Are you the author of Flisk Deploy Fly?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/flisk-sh-flisk-deploy-fly)
---
name: flisk-deploy-fly
description: Take a stack that already works under `flisk up` to Fly.io with that host's own tooling - `fly.toml` per service, `fly secrets set`, `fly deploy`. It maps each service.json (ports, health checks, dependencies, env) to production artifacts written for the host, never the local `.autogenerated/` files. Use when the user wants to ship a working Flisk stack to Fly.io. Flisk itself stays local; for Helm, Argo CD or Kustomize pipelines use flisk-helm.
license: MIT
compatibility: Requires a working local Flisk stack first. flyctl recommended.
metadata:
author: flisk-sh
version: "1.0"
---
# Deploy to Fly.io
Flisk is local-only. This skill covers deploying to Fly.io.
## Workflow
1. Confirm the stack works locally: `flisk doctor && flisk up <stack>`.
2. Extract the contract from service.json.
3. Create a fly.toml per service or use a multi-app setup.
4. Set secrets with `fly secrets set`.
5. Deploy with `fly deploy` and verify health.
## Guardrails
- Use production Dockerfiles, not local generated ones.
- Keep local and production configs separate.
