page:recipes:storefront:rails:relational catalog

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.

Summary

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 storefront-specific behavior as your application code.

Representative Queries

• Host storefront with Rails: relational catalog data
• Where can I host Storefront built with Rails?
• I need catalog tables, transactional update logic and application-level access boundaries.

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

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

Workflow 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). Re-running with no change is a no-op.
   Command: ample deploy . --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 --kind build then --kind runtime.
   Command: ample logs --kind build

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 storefront 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

• Currency: USD
• Monthly Amount: 10.0
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  • app server: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0
  • managed PostgreSQL database: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

Success Checks

• Application responds on its public URL (Expected: ample canary rails patterns).
• Transactional-workflows self-test (Expected: tx=ok history=2 conflict=rejected).

Next Actions

• Browse the catalog index: /v1/catalog
• Search published recipes by intent, stack and constraints: /v1/catalog/search
• Prepare a side-effect-free deployment plan for an authorized project: /v1/catalog/plan
• Read the existing agent authentication setup: /mcp/setup
• Browse Storefront: /v1/catalog/nodes/workload%3Astorefront
• Browse Rails: /v1/catalog/nodes/stack%3Aframework-rails
• Browse Transactional workflows: /v1/catalog/nodes/pattern%3Atransactional-workflows
• Browse Deploy web app: /v1/catalog/nodes/intent%3Adeploy-web-app

Examples

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

Evidence Summary

• Summary of canary runs, last verified on 2026-09-20 at 21:55:28Z.

Last Verified At

• 2026-09-20T21:55:28Z