Host approval workflow with Rails: relational workspace data

Deploy an approval workflow built with Rails on Ample using the relational records 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: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Not separately tested: your record schema, states and access rules; treat the approval workflow-specific behavior as your application code.

Representative Queries

• Host approval workflow with Rails: relational workspace data
• Where can I host Approval workflow built with Rails?
• I need a workspace-specific schema, state transitions and access rules.

Resource Requirements

• Compute
• Postgres

Infrastructure Requirements

• Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
• 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.

Framework

Rails

Workload

Approval workflow

Release Status

published

Support Status

verified

Execution Status

ready

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

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 relational records: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). 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.
   ample deploy . --name --public

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

Examples

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

Success Checks

• App responds on its public URL (expected: ample canary rails patterns)
• Relational-records self-test (expected: records=ok transitions=true isolation=true)

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 approval workflow itself (your record schema, states and access rules) 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
• Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Next Actions

1. Browse the catalog index
2. Search published recipes by intent, stack and constraints
3. Prepare a side-effect-free deployment plan for an authorized project
4. Read the existing agent authentication setup
5. Browse Approval workflow
6. Browse Rails
7. Browse Relational records
8. Browse Deploy web app