Host marketplace with Rails: relational catalog data · Ample Computer

Host marketplace with Rails: relational catalog data

Deploy a marketplace 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 marketplace-specific behavior (your domain records, validation rules and concurrency policy) is your application code on that verified basis.

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. 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 needs an answer first). Re-running with no change is a no-op.

$ ample deploy . --name <app-name> --public
  1. 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

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

  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); 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).

  2. November 5, 2026 · canary run
    The same Rails app deployed with a --release-command migration; the marker it created was readable after activation.

Tested examples

What it doesn’t cover