# Migrate Fly.io app: Next.js

Move Next.js 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.

**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.

### Workflow 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**: `next build` then `next start -H 0.0.0.0 -p $PORT` on the node-22 template. Pass the exported variables with --env; keep the source running.
   ```bash
   ample deploy . --name  --public --env-file .env.production
   ```
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.

### Limitations
- Documentation only: nothing is executed automatically and no execution binding is offered.
- The source-side procedure is documented from Fly.io app's standard tooling and was not executed in this catalog's evidence; the destination side was verified with the pattern fixture.

### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: $10.00
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty

#### Components
- **App server**: size = s-1vcpu-1gb, quantity = 1.0, monthly amount = $5.00
- **Managed PostgreSQL database**: size = s-1vcpu-1gb, quantity = 1.0, monthly amount = $5.00

### Success Checks
1. Destination app responds on its public URL
   - **Kind**: http_get
   - **Path**: /
   - **Expect**: ample canary next js patterns
2. Configuration-secrets check from the destination example
   - **Kind**: http_get
   - **Path**: /p/configuration-secrets
   - **Expect**: see the pattern fixture checks
3. Data or object counts and checksums match the source
   - **Kind**: manual
   - **Expect**: operator comparison before cutover.