## Host knowledge base with React Router: object-stored public media

Deploy a knowledge base built with React Router on Ample using the public media library 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, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables, and a published bucket serves public assets from the CDN host. Verified on React Router: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. Not separately tested: your media processing, object layout and cache policy; treat the knowledge base-specific behavior as your application code.

### Representative Queries
- Host knowledge base with React Router: object-stored public media
- Where can I host Knowledge base built with React Router?
- I need an object layout, public asset URL policy and CDN delivery configuration.

### Resource Requirements 
- Compute 
- Postgres 
- S3-compatible object storage 
- CDN

### Infrastructure Requirements
1. **Compute**  
   Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
2. **Postgres**  
   Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
3. **S3-compatible object storage**  
   Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.
4. **CDN**  
   The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

### Workflow Steps
1. **Build and start**  
   `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**  
   The fixture's module implements public media library: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. Copy the approach into your schema; keep migrations idempotent and run them with `--release-command`.
3. **Wire object storage**  
   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**  
   `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**  
   Fetch the live URL and the pattern self-test route(s) `/p/public-media-library` from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.

### Examples
- **React Router pattern fixture**  
  Multi-pattern React Router app whose public media library module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

### 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 knowledge base itself (your media processing, object layout and cache policy) is application code and was not separately tested; the pattern checks are what was verified.

### Success Checks 
1. App responds on its public URL  
   **Expected Response:** `ample canary react router patterns`
2. Public-media-library self-test  
   **Expected Response:** a CDN URL whose content is served publicly.

### Cost Estimate
- **Currency:** USD  
- **Monthly Amount:** 10.0  
- **Note:** Always-on monthly price; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.