Migrate Render web service: Rails · Ample Computer

Migrate Render web service: Rails

Move Rails compute from Render web service 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 and secret files from the Render dashboard into an env file kept out of the repository. Move separately: Render cron jobs become ample job schedules, disks become Ample volumes, and private services connect with --link. Cutover: Add the custom domain with ample domain add, update DNS from the Render target, keep the Render service until verified, then suspend it. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

Verified November 6, 2026

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 Render web service provides beyond the component you are moving. Plan these separately: Render cron jobs become ample job schedules, disks become Ample volumes, and private services connect with --link.

  2. Source step 1. Copy environment variables and secret files from the Render dashboard into an env file kept out of the repository.

  3. Source step 2. Translate the Render build and start commands (or render.yaml) into the repository's manifest or --build-command/--start.

  4. Source step 3. Note Render-only features in use: background workers, cron jobs, disks, private services.

  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, update DNS from the Render target, keep the Render service until verified, then suspend it.

  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

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 Render web service uses the vendor's standard tooling.

Tested examples

What it doesn’t cover