## 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
- Host client portal with Rails: application activity history
- Where can I host Client portal built with Rails?
- I need an application-owned event schema and tested history queries; not native platform audit logs.

### Resource Requirements
- **primitive:compute**
- **primitive:postgres**

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

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

### 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
- 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 client portal 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  
- **Authoritative**: true  
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
- **Components**:  
  1. **App server**: size s-1vcpu-1gb, quantity 1.0, monthlyAmount 5.0  
  2. **Managed PostgreSQL database**: size s-1vcpu-1gb, quantity 1.0, monthlyAmount 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.

### 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
- Region availability is unknown until a verified region fact is recorded.
- Compliance attestations are unknown; none are claimed.

### Formats
- **HTML**: [ample.computer](/content/recipes/client-portal/rails/activity-history/index.html)  
- **Markdown**: [ample.computer](/content/recipes/client-portal/rails/activity-history.md)  
- **JSON**: [api.ample.computer](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Aclient-portal%3Arails%3Aactivity-history)

### Next Actions
- **Browse the catalog index**:  
   - **Method**: GET  
   - **Path**: /v1/catalog  
   - **Requires Authentication**: false

- **Search published recipes by intent, stack and constraints**:  
   - **Method**: POST  
   - **Path**: /v1/catalog/search  
   - **Parameters**: {"body":{"limit":5,"query":"Host client portal with Rails: application activity history"}}  
   - **Requires Authentication**: false

- **Prepare a side-effect-free deployment plan for an authorized project**:  
   - **Method**: POST  
   - **Path**: /v1/catalog/plan  
   - **Parameters**: {"body":{"inputs":{},"projectId":"","recipeId":"page:recipes:client-portal:rails:activity-history","recipeRevision":"r1"}}  
   - **Requires Authentication**: true

- **Read the existing agent authentication setup**:  
   - **Method**: GET  
   - **Path**: /mcp/setup  
   - **Requires Authentication**: false

- **Browse Client portal**:  
   - **Method**: GET  
   - **Path**: /v1/catalog/nodes/workload%3Aclient-portal  
   - **Requires Authentication**: false

- **Browse Rails**:  
   - **Method**: GET  
   - **Path**: /v1/catalog/nodes/stack%3Aframework-rails  
   - **Requires Authentication**: false

- **Browse Transactional workflows**:  
   - **Method**: GET  
   - **Path**: /v1/catalog/nodes/pattern%3Atransactional-workflows  
   - **Requires Authentication**: false

- **Browse Deploy web app**:  
   - **Method**: GET  
   - **Path**: /v1/catalog/nodes/intent%3Adeploy-web-app  
   - **Requires Authentication**: false