Apply database schema changes for Sinatra

Summary

Schema changes for a Sinatra app on Ample. Verified on Sinatra: 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 rackup (config.ru) reading PORT on the ruby-3.4 template.

Infrastructure requirements

• Compute: verified (Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.)
• Postgres: verified (Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.)

Prerequisites

• A Sinatra project (bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma via rackup (config.ru) reading PORT on the ruby-3.4 template)
• A PostgreSQL driver reading DATABASE_URL at runtime
• An Ample account token with servers:write, databases:read

Exact tested configuration

• template: ruby-3.4
• runtime: ruby
• size: s-1vcpu-1gb
• install: bundle config set --local path vendor/bundle && bundle config set --local without 'development test' && bundle install
• start: bundle exec rackup -o 0.0.0.0 -p $PORT

Steps

1. Build and start. bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma via rackup (config.ru) reading PORT on the ruby-3.4 template; 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"
   

3. 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
   

Tested examples

• Sinatra pattern fixture (tests/deploy-canaries/sinatra-patterns): Verified schema changes on Sinatra.

Success checks

• app responds on its public URL (/ on the live URL, expect ample canary sinatra patterns)
• migrated check from the example (/p/migrated on the live URL, expect see the pattern fixture checks)

Limitations

• Verified on the ruby-3.4 template at s-1vcpu-1gb; other sizes and Sinatra major versions are not verified.
• Region, compliance attestations and request-duration limits are unknown and not claimed.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.

Cost estimate

Estimated 10.00 USD per month (size prices from pricing.toml at build revision a1b8c38919e59cd035ebabaced73cf84ece24371).

• app server x1 s-1vcpu-1gb: 5.00 USD
• managed PostgreSQL database x1 s-1vcpu-1gb: 5.00 USD

Verification evidence

• canary_run on 2026-09-20T23:45:31Z at revision 4d1511e574302f3904b75088bd4048a0975218b3-dirty (CLI 0.1.21): Sinatra pattern fixture deployed on Ample (bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma via rackup (config.ru) reading PORT on the ruby-3.4 template); for this guide: a --release-command migration ran before activation and its marker was readable by the live app (migrated=release-ok). (expires 2027-03-19T23:45:31Z)

Last verified: 2026-09-20T23:45:31Z

Execution binding

MCP tool ample_deploy (registry mcp:ample_deploy), schema hash 876465fce906da0c observed 2026-09-21T03:19:59.461917+00:00 at revision 49962bcade4f, binding state current, required scopes: servers:write, databases:read.