Migrate Heroku app: Rails · Ample Computer
Migrate Heroku app: Rails
Move Rails compute from Heroku 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 config vars with heroku config -s -a <app> into an env file kept out of the repository. Move separately: Heroku Scheduler jobs become ample job schedules and release-phase tasks use --release-command; add-ons other than Postgres map to Ample managed databases and buckets or stay with their provider. Cutover: Add the custom domain with ample domain add, update DNS from the Heroku DNS target, keep the Heroku app until verified, then scale it down. 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
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgresverified
Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
You need
- Authorized access to the Heroku 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
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
Inventory the source. List what Heroku app provides beyond the component you are moving. Plan these separately: Heroku Scheduler jobs become
ample jobschedules and release-phase tasks use--release-command; add-ons other than Postgres map to Ample managed databases and buckets or stay with their provider.Source step 1. Export config vars with
heroku config -s -a <app>into an env file kept out of the repositorySource step 2. Translate the
Procfileweb process into the start command (--startor the package manifest's start script); worker processes need a separate--kind workerserviceSource step 3. Note buildpacks and add-ons in use; managed databases replace Heroku Postgres, other add-ons need their own plan
Deploy on Ample in parallel. bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma via
rails serverreading 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
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).
Cut over. Add the custom domain with
ample domain add, update DNS from the Heroku DNS target, keep the Heroku app until verified, then scale it down.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 viarails serverreading 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 Heroku app uses the vendor's standard tooling.
Tested examples
- Rails pattern fixture (destination). Verified destination basis: Rails compute.
What it doesn’t cover
- A step-by-step guide: each stage is an ordinary
ample deploy,ample databaseorample bucketcommand you run. - The destination side was verified on Ample with the pattern fixture; the source-side steps use Heroku app's standard tooling.
- Plan separately: Heroku Scheduler jobs become
ample jobschedules and release-phase tasks use--release-command; add-ons other than Postgres map to Ample managed databases and buckets or stay with their provider. - Verified on the ruby-3.4 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector. Back up and restore with pg_dump and pg_restore.