page:recipes:client portal:rails:activity history

Host client portal with Rails: application activity history

Summary

Deploy a client portal 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 client portal-specific behavior as your application code.

Representative Queries

Resource Requirements

Infrastructure Requirements

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

Client portal

Release Status

published

Support Status

verified

Execution Status

ready

Prerequisites

Tested Configuration

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

Examples

Success Checks

  1. App responds on its public URL

    • Kind: http_get
    • Path: /
    • Expect: ample canary rails patterns

  2. Transactional-workflows self-test

    • Kind: http_get
    • Path: /p/transactional-workflows
    • Expect: tx=ok history=2 conflict=rejected

Limitations

Cost Estimate

Evidence Summary

  1. Kind: canary_run

    • Summary: 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).
    • Observed At: 2026-09-20T21:55:28Z
    • Implementation Revision: 4f7cb9813c1f-dirty (CLI 4f7cb98)
    • Expires At: 2027-03-19T21:55:28Z
    • Scope:
      • Checks: [/p/transactional-workflows]
      • Pattern: pattern:transactional-workflows
      • Template: ruby-3.4

  2. Kind: canary_run

    • Summary: The same Rails app deployed with a --release-command migration; the marker it created was readable after activation.
    • Observed At: 2026-09-20T21:55:28Z
    • Implementation Revision: 4f7cb9813c1f-dirty (CLI 4f7cb98)
    • Expires At: 2027-03-19T21:55:28Z
    • Scope:
      • Pattern: pattern:transactional-workflows

Last Verified At

2026-09-20T21:55:28Z

Unknowns

Formats

Next Actions