Agent skill · software engineering · jeremylongshore
flyio-core-workflow-b
Design Fly.io Managed Postgres, Fly Volumes, and private 6PN connectivity with explicit durability boundaries. Use when an app needs persistent data or private service access. Trigger with: "add Fly Managed Postgres", "plan Fly volume storage", "connect Fly apps privately".
Why this skill is useful
Adds executable scripts for setting up Fly.io Postgres, persistent volumes, and private networking that aren't in public docs.
What it needs
Requires fly installed locally. Requires fly.io account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Fly.io Managed Data and Private Networking Overview Choose the data service before writing commands: Managed Postgres is a separate fully managed service, while Fly Volumes are region-bound local NVMe storage attached to Machines. Private 6PN networking connects apps in the same organization but does not make either storage model globally consistent. Prerequisites Workload, data classification, residency, availability, recovery, and latency requirements Approved regions and network boundary Restore-test owner and application cutover plan Instructions Step 1: Select the persistence model Use Managed Postgres when the workload needs the provider-managed database service. Use a Fly Volume only for software that owns replication and recovery or for region-local state. Step 2: Place data intentionally Choose a supported Managed Postgres region close to the app or create volumes in the same region as their Machines. Query current region availability instead of hardcoding a global count. Step 3: Define private connectivity Use organization 6PN addresses and the documented .internal DNS name appropriate to the service, region, process group, or Machine. Document cross-organization exceptions separately. Step 4: Protect the data For Managed Postgres, capture plan, backup, failover, pooling, and support boundaries. For volumes, set snapshot retention and add independent backup or replication when recovery objectives exceed snapshot coverage. Step 5: Test failure and restore Prove application reconnect behavior, credential rotation, snapshot or managed restore procedure, regional loss response, and data reconciliation in a non-production target. Step 6: Cut over with rollback Freeze writes if required, migrate through an approved method, validate counts and application behavior, then retain the old data path until rollback expiry. Authentication Keep database credentials in Fly App secrets or an approved external secret manager, not in fly.toml or receipts. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/flyio-core-workflow-b