# Migrate Fly.io app: Express

Move Express compute from Fly.io app to Ample, one component at a time. Destination verified on Ample: the app built, started and answered on its public HTTPS URL with encrypted configuration delivered.

## Migration Summary
- **Source procedure**: Export secrets and env from `fly.toml` [env] and `fly secrets list` (values must come from your own records; Fly does not reveal secret values).
- **Not migrated automatically**: Multi-region placement, Fly Machines API, volumes, and 6PN private networking are not migrated; region is an unknown fact on Ample.
- **Cutover**: Add the custom domain with `ample domain add`, update DNS from the Fly target, keep the Fly app until verified, then scale it to zero.
- **Rollback**: Keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

## Prerequisites
- Authorized access to the Fly.io app source and its export tooling
- An inventory of every component in scope and out of scope
- A validated backup or copy before any cutover
- An Ample account token with servers:write, databases:read

## Migration Steps
1. **Inventory the source**: List what Fly.io app provides beyond the component you are moving. Out of scope here: Multi-region placement, Fly Machines API, volumes and 6PN private networking are not migrated; region is an unknown fact on Ample.
2. **Source step 1**: Export secrets and env from `fly.toml` [env] and `fly secrets list` (values must come from your own records; Fly does not reveal secret values).
3. **Source step 2**: Translate `fly.toml` services and the Dockerfile or buildpack into a Node or Python source deploy; Ample builds from source on its templates.
4. **Source step 3**: Note Fly-only features in use: multi-region placement, machines API, volumes, private networking.
5. **Deploy on Ample in parallel**: `npm install, npm run build --if-present, npm run start` on the node-22 template. Pass the exported variables with `--env`; keep the source running.
6. **Validate before cutover**: Run the app's own checks and, for data, compare counts and checksums; the example checks are the pattern self-tests (/p/configuration-secrets, /p/relational-records).
7. **Cut over**: Add the custom domain with `ample domain add`, update DNS from the Fly target, keep the Fly app until verified, then scale it to zero.
8. **Rollback**: Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation.

## Examples
### Express pattern fixture (destination)
- **Description**: Verified destination basis: Express compute.
- **Source Reference**: tests/deploy-canaries/express-patterns

## Success Checks
- Destination app responds on its public URL (HTTP GET /)
  - Expect: ample canary express patterns
- Configuration-secrets check from the destination example (HTTP GET /p/configuration-secrets)
  - Expect: see the pattern fixture checks
- Relational-records check from the destination example (HTTP GET /p/relational-records)
  - Expect: see the pattern fixture checks
- Data or object counts and checksums match the source (manual)
  - Expect: operator comparison before cutover.

## Limitations
- Documentation only: nothing is executed automatically and no execution binding is offered.
- No full source-product parity is claimed: Multi-region placement, Fly Machines API, volumes, and 6PN private networking are not migrated; region is an unknown fact on Ample.
- Verified on the node-22 template at s-1vcpu-1gb; region, compliance, and request-duration limits are unknown.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Components**:
  - App server: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0
  - Managed PostgreSQL database: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0
- **Note**: Destination always-on monthly price of the tested sizes; apps auto-pause when idle. Source costs are unknown to Ample.

## Evidence Summary
- **Kind**: canary_run
- **Summary**: Destination side verified: the Express pattern fixture deployed on Ample (npm install, npm run build --if-present, npm run start on the node-22 template) and its checks passed. 
- **Observed At**: 2026-09-21T02:34:39Z
- **Expires At**: 2027-03-20T02:34:39Z

## Last Verified At
- 2026-09-21T02:34:39Z

## Formats
- **HTML**: https://ample.computer/migrate/fly-io-app/express
- **Markdown**: https://ample.computer/migrate/fly-io-app/express.md
- **JSON**: https://api.ample.computer/v1/catalog/recipes/page%3Amigrate%3Afly-io-app%3Aexpress

## Next Actions
- **Browse the catalog index**: GET /v1/catalog
- **Search published recipes by intent**: POST /v1/catalog/search
- **Prepare a side-effect-free deployment plan**: POST /v1/catalog/plan
- **Read the existing agent authentication setup**: GET /mcp/setup
- **Browse Fly.io app**: GET /v1/catalog/nodes/migration%3Afly-io-app
- **Browse Express**: GET /v1/catalog/nodes/stack%3Aframework-express
- **Browse Migrate compute**: GET /v1/catalog/nodes/intent%3Amigrate-compute