Migrate Netlify web app: Rails · Ample Computer

Migrate Netlify web app: Rails

Move Rails compute from Netlify web 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: Copy environment variables from Site configuration (or netlify env:list) into an env file kept out of the repository. Move separately: Netlify Functions and Edge Functions become routes in the app or a separate Ample service; _redirects/_headers rules, Forms and Identity move into the app or its framework. Cutover: Add the custom domain with ample domain add, set the documented DNS records, keep the Netlify site until verified, then remove the domain from Netlify. 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

install bundle config set --local path vendor/bundle && bundle config set --local without 'development test' && bundle install
run time ruby
sizes-1vcpu-1gb
start bundle exec rails server -b 0.0.0.0 -p $PORT
template ruby-3.4

Steps

  1. Inventory the source. List what Netlify web app provides beyond the component you are moving. Plan these separately: Netlify Functions and Edge Functions become routes in the app or a separate Ample service; _redirects/_headers rules, Forms and Identity move into the app or its framework.

  2. Source step 1. Copy environment variables from Site configuration (or netlify env:list) into an env file kept out of the repository

  3. Source step 2. Translate netlify.toml build settings (command, publish directory) into the repository's own build script; Ample runs the detected build

  4. Source step 3. List Netlify-only features in use: functions, edge functions, forms, identity, redirects and headers rules

  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
  1. 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).

  2. Cut over. Add the custom domain with ample domain add, set the documented DNS records, keep the Netlify site until verified, then remove the domain from Netlify.

  3. 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 Netlify web app uses the vendor's standard tooling.

Tested examples

What it doesn’t cover