### Host campaign site with Rails: Postgres-backed content

Deploy a campaign site 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, and a published bucket serves public assets from the CDN host. 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).

#### Representative Queries
- Host campaign site with Rails: Postgres-backed content
- Where can I host Campaign site built with Rails?
- I need a content schema, publishing workflow and cache behavior after content updates.

### Resource Requirements
- `primitive:compute`
- `primitive:postgres`
- `primitive:cdn`

### 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.
- **CDN**: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

### 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).
- A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables.
- An Ample account token with servers:write, databases:read, buckets: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).
3. **Wire object storage**: Create the bucket(s), then pass endpoint, region, bucket and keys as --env values.
4. **Deploy**: Run the synchronous deploy once and read the result.
5. **Verify**: Fetch the live URL and the pattern self-test route(s).

### 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 campaign site itself (your record schema, states and access rules) is application code and was not separately tested.

### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Components**:
  - **App Server**: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0
  - **Managed PostgreSQL Database**: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

### Evidence Summary
- **Canary Run**: Rails pattern fixture deployed on Ample; checks passed for relational-records and configuration-secrets.

### Next Actions
- [Browse the catalog index](https://api.ample.computer/v1/catalog)
- [Search published recipes by intent, stack and constraints](https://api.ample.computer/v1/catalog/search)
- [Prepare a side-effect-free deployment plan for an authorized project](https://api.ample.computer/v1/catalog/plan)
- [Read the existing agent authentication setup](https://api.ample.computer/mcp/setup)
- [Browse Campaign site](https://api.ample.computer/v1/catalog/nodes/workload%3Acampaign-site)
- [Browse Rails](https://api.ample.computer/v1/catalog/nodes/stack%3Aframework-rails)
- [Browse Relational records](https://api.ample.computer/v1/catalog/nodes/pattern%3Arelational-records)
- [Browse Deploy web app](https://api.ample.computer/v1/catalog/nodes/intent%3Adeploy-web-app)