Migrate DigitalOcean Droplet app: Rails · Ample Computer

Migrate DigitalOcean Droplet app: Rails

Move Rails compute from DigitalOcean Droplet 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: Collect the process environment from the droplet (systemd unit, PM2 or supervisor config) into an env file kept out of the repository. Move separately: cron jobs become ample job schedules, local upload directories move to a bucket and data to a managed database; Ample handles firewalling. Cutover: Add the custom domain with ample domain add, update DNS from the droplet IP, keep the droplet until verified, then power it off. 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 DigitalOcean Droplet app provides beyond the component you are moving. Plan these separately: cron jobs become ample job schedules, local upload directories move to a bucket and data to a managed database; Ample handles firewalling.

  2. Source step 1. Collect the process environment from the droplet (systemd unit, PM2 or supervisor config) into an env file kept out of the repository

  3. Source step 2. Replace the droplet's process manager and reverse proxy with the repository's start command; Ample provides HTTPS and supervision

  4. Source step 3. Inventory what else runs on the droplet: databases, cron, local uploads

  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 droplet IP, keep the droplet until verified, then power it off.

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 DigitalOcean Droplet 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 database` or `ample bucket` command you run.
- The destination side was verified on Ample with the pattern fixture; the source-side steps use DigitalOcean Droplet app's standard tooling.
- Plan separately: cron jobs become `ample job` schedules, local upload directories move to a bucket and data to a managed database; Ample handles firewalling.
- 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.