Host storefront with Rails: relational catalog data · Ample Computer
Host storefront with Rails: relational catalog data
Deploy a storefront 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). The storefront-specific behavior (your domain records, validation rules and concurrency policy) is your application code on that verified basis.
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 noDATABASE_URLis supplied.
You need
- 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 serverreading PORT on the ruby-3.4 template withRAILS_ENV=production) - A PostgreSQL driver reading
DATABASE_URLat runtime (auto-provisioned when omitted, or supplied with --env) - 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
Build and start. 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 withRAILS_ENV=production. The server must bind 0.0.0.0 on PORT.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.Deploy. Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 needs an answer first). Re-running with no change is a no-op.
$ ample deploy . --name <app-name> --public
- 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 buildthen--kind runtime.
$ ample logs <deployment_id> --kind build
How it was checked
✓ app responds on its public URL· http get/ → “ample canary rails patterns”
✓ transactional-workflows self-test· http get/p/transactional-workflows → “tx=ok history=2 conflict=rejected”
Evidence
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 viarails serverreading PORT on the ruby-3.4 template withRAILS_ENV=production); checks passed for transactional-workflows and configuration-secrets. Pattern proof: 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).November 5, 2026 · canary run
The same Rails app deployed with a--release-commandmigration; the marker it created was readable after activation.
Tested examples
- Rails pattern fixture. Multi-pattern Rails app whose transactional workflows module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
What it doesn’t cover
- Verified on the ruby-3.4 template at s-1vcpu-1gb with the example fixture.
- The pattern checks verified the platform side; the storefront itself (your domain records, validation rules and concurrency policy) is your application code.
- Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.