page:recipes:member portal:rails:activity history

Host member portal with Rails: application activity history

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

Representative Queries

Prerequisites

Infrastructure Requirements

  1. Compute

    • Status: verified
    • Summary: 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

    • Status: verified
    • Summary: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

Tested Configuration

Workflow Steps

  1. Build and start

    • Body: 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

    • Body: 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

    • Body: 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

    • Body: 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

Success Checks

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.
    • 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

Next Actions

  1. Browse the catalog index

    • Action Id: browse-catalog
    • Operation Id: catalog_index
    • Method: GET
    • Relative Path: /v1/catalog

  2. Search published recipes by intent, stack and constraints

    • Action Id: search-recipes
    • Operation Id: search_recipes
    • Method: POST
    • Relative Path: /v1/catalog/search
    • Parameters: { "body": { "limit": 5, "query": "Host member portal with Rails: application activity history" } }

  3. Prepare a side-effect-free deployment plan for an authorized project

    • Action Id: plan:page:recipes:member-portal:rails:activity-history
    • Operation Id: plan_deployment
    • Method: POST
    • Relative Path: /v1/catalog/plan
    • Parameters: { "body": { "inputs": {}, "projectId": "", "recipeId": "page:recipes:member-portal:rails:activity-history", "recipeRevision": "r1" } }

  4. Read the existing agent authentication setup

    • Action Id: auth-setup
    • Operation Id: existing_auth_setup
    • Method: GET
    • Relative Path: /mcp/setup

  5. Browse Member portal

    • Action Id: browse:workload:member-portal
    • Operation Id: browse_node
    • Method: GET
    • Relative Path: /v1/catalog/nodes/workload%3Amember-portal

  6. Browse Rails

    • Action Id: browse:stack:framework-rails
    • Operation Id: browse_node
    • Method: GET
    • Relative Path: /v1/catalog/nodes/stack%3Aframework-rails

  7. Browse Transactional workflows

    • Action Id: browse:pattern:transactional-workflows
    • Operation Id: browse_node
    • Method: GET
    • Relative Path: /v1/catalog/nodes/pattern%3Atransactional-workflows

  8. Browse Deploy web app

    • Action Id: browse:intent:deploy-web-app
    • Operation Id: browse_node
    • Method: GET
    • Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app