Host digital downloads with Rails: relational catalog data

Summary

Deploy a digital downloads built with Rails on Ample using the transactional workflows pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL. Verified on Rails: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). Not separately tested: your domain records, validation rules and concurrency policy; treat the digital downloads-specific behavior as your application code.

Infrastructure requirements

• Verified Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
• Verified Postgres: 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 Rails project that builds and starts with the documented commands (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)
• A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
• 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 rails server -b 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 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. Implement the pattern on PostgreSQL. The fixture's module implements transactional workflows: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

3. Deploy. Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked).

   ample deploy . --name <app-name> --public
   

4. Verify. Fetch the live URL and the pattern self-test route(s) (/p/transactional-workflows) from the example; then run your own checks. On failure read ample logs <deployment_id> --kind build then --kind runtime.

   ample logs <deployment_id> --kind build
   

Tested examples

• Rails pattern fixture (tests/deploy-canaries/rails-patterns): Multi-pattern Rails app whose transactional workflows module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

Success checks

• app responds on its public URL (/ on the live URL, expect ample canary rails patterns)
• transactional-workflows self-test (/p/transactional-workflows on the live URL, expect tx=ok history=2 conflict=rejected)

Limitations

• Verified on the ruby-3.4 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Rails major versions are not verified.
• The digital downloads itself (your domain records, validation rules and concurrency policy) is application code and was not separately tested; the pattern checks are what was verified.
• Region, compliance attestations and request-duration limits are unknown and not claimed.
• Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.

Cost estimate

Estimated 10.00 USD per month.

• 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-20T21:55:28Z at revision 4f7cb9813c1f-dirty (CLI 4f7cb98): Rails pattern fixture deployed on Ample; checks passed for transactional-workflows and configuration-secrets.

Execution binding

MCP tool ample_deploy, schema hash 876465fce906da0c.