Apply database schema changes for Rails · Ample Computer

Apply database schema changes for Rails

Schema changes for a Rails app on Ample. Verified on Rails: a --release-command migration ran before activation and its marker was readable by the live app (migrated=release-ok). Build and start: 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.

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. Build and start. 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; the server must bind 0.0.0.0 on PORT.

  2. Run migrations as the release command. Ample runs the command before activation and fails the release if it exits non-zero; keep migrations idempotent.

   $ ample deploy . --name <app-name> --public --release-command "python3 migrate.py"
  1. Verify. Fetch the live URL and /p/migrated on the example; on failure read the build and runtime logs.
   $ ample logs <deployment_id> --kind build

How it was checked

✓app responds on its public URL· http get/ → “ample canary rails patterns”
✓migrated check from the example· http get/p/migrated → “see the pattern fixture checks”

Evidence

  1. November 6, 2026 · canary run
    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); for this guide: a --release-command migration ran before activation and its marker was readable by the live app (migrated=release-ok).

Tested examples

What it doesn’t cover