## Host company website with React Router: Postgres-backed content

Deploy a company website built with React Router 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 React Router: 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). Not separately tested: your record schema, states and access rules; treat the company website-specific behavior as your application code.

### Representative Queries
- Host company website with React Router: Postgres-backed content
- Where can I host Company website built with React Router?
- I need a content schema, publishing workflow and cache behavior after content updates.

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

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

3. **CDN**  
   - Status: verified  
   - Summary: 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 React Router project that builds and starts with the documented commands (react-router build then react-router-serve on the node-22 template)
- 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**  
   - Command: `react-router build then react-router-serve on the node-22 template. The server must bind 0.0.0.0 on PORT.`

2. **Implement the pattern on PostgreSQL**  
   - Body: 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). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

3. **Wire object storage**  
   - Body: Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing. Keep private data in an unpublished bucket. Publish only the bucket that serves public assets and reference its CDN URL.

4. **Deploy**  
   - Command: `ample deploy . --name  --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=...`

5. **Verify**  
   - Command: `ample logs  --kind build`  
 - Body: Fetch the live URL and the pattern self-test route(s) (/p/relational-records) from the example; then run your own checks. On failure read.

### Cost Estimate
- **Monthly Amount**: $10.0 USD
- **Basis**: Size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
- **Components**:
  1. App server
     - Size: s-1vcpu-1gb
     - Monthly Amount: $5.0
  2. Managed PostgreSQL database
     - Size: s-1vcpu-1gb
     - Monthly Amount: $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.

### Examples
1. **React Router pattern fixture**  
   - Description: Multi-pattern React Router app whose relational records module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
   - Source Ref: tests/deploy-canaries/react-router-patterns

### Success Checks
1. **App responds on its public URL**  
   - Kind: http_get  
   - Path: /  
   - Expect: ample canary react router patterns

2. **Relational-records self-test**  
   - Kind: http_get  
   - Path: /p/relational-records  
   - Expect: records=ok transitions=true isolation=true

### Limitations
- Verified on the node-22 template at s-1vcpu-1gb with the example fixture; other sizes, templates, and React Router major versions are not verified.
- The company website itself (your record schema, states, and access rules) 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.

### Next Actions
1. **Browse the catalog index**  
   - Method: GET  
   - Relative Path: /v1/catalog  
2. **Search published recipes by intent, stack and constraints**  
   - Method: POST  
   - Relative Path: /v1/catalog/search  
   - Parameters: {"body":{"limit":5,"query":"Host company website with React Router: Postgres-backed content"}}
3. **Prepare a side-effect-free deployment plan for an authorized project**  
   - Method: POST  
   - Relative Path: /v1/catalog/plan  
   - Parameters: {"body":{"inputs":{},"projectId":"","recipeId":"page:recipes:company-website:react-router:relational-content","recipeRevision":"r1"}}