## Host reporting dashboard with Rails: relational workflow state

### Summary
Deploy a reporting dashboard 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 reporting dashboard-specific behavior as your application code.

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

### Execution Steps
1. **Build and start**  
   `bundle install` into vendor/bundle from Gemfile.lock (development and test groups skipped), then start 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 <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`

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

### Success Checks
- App responds on its public URL
- Transactional-workflows self-test

### 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 reporting dashboard 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.

### Cost Estimate
- Currency: USD  
- Monthly Amount: $10.00  
- 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.00  
   - Managed PostgreSQL database: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: $5.00
- Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

### Next Actions
- **Browse the catalog index**  
  Method: GET  
  Relative Path: /v1/catalog
- **Search published recipes by intent**  
  Method: POST  
  Relative Path: /v1/catalog/search
- **Prepare a deployment plan**  
  Method: POST  
  Relative Path: /v1/catalog/plan