Migrate Fly.io app: Rails · Ample Computer

Migrate Fly.io app: Rails

Move Rails 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). Move separately: Fly volumes become Ample volumes and 6PN private services connect with --link; Ample runs each app in the USA or Europe and handles placement, so Fly Machines API calls drop out. 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.

What it runs on

You need

Exact tested configuration

installbundle config set --local path vendor/bundle && bundle config set --local without 'development test' && bundle install

runtimeruby

sizes-1vcpu-1gb

startbundle exec rails server -b 0.0.0.0 -p $PORT

templateruby-3.4

Steps

  1. Inventory the source. List what Fly.io app provides beyond the component you are moving. Plan these separately: Fly volumes become Ample volumes and 6PN private services connect with --link; Ample runs each app in the USA or Europe and handles placement, so Fly Machines API calls drop out.

  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. bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma via rails server reading PORT on the ruby-3.4 template with RAILS_ENV=production. Pass the exported variables with --env; keep the source running.

    $ ample deploy . --name <app-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.

How it was checked

✓ destination app responds on its public URL· http get/ → “ample canary rails patterns”
✓ configuration-secrets check from the destination example· http get/p/configuration-secrets → “see the pattern fixture checks”
✓ relational-records check from the destination example· http get/p/relational-records → “see the pattern fixture checks”
✓ data or object counts and checksums match the source· manual → “operator comparison before cutover”

Evidence

  1. November 6, 2026 · canary run
    Destination side verified: the Rails pattern fixture deployed on Ample (bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma via rails server reading PORT on the ruby-3.4 template with RAILS_ENV=production) and its checks passed (the app built, started and answered on its public HTTPS URL with encrypted configuration delivered). The source-side export from Fly.io app uses the vendor's standard tooling.

Tested examples

What it doesn’t cover