# Host knowledge base with Next.js: object-stored public media

Deploy a knowledge base built with Next.js 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 Next.js: 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 Next.js: object-stored public media
- Where can I host Knowledge base built with Next.js?
- I need an object layout, public asset URL policy and CDN delivery configuration.

## Prerequisites
- A Next.js project that builds and starts with the documented commands (`next build` then `next start -H 0.0.0.0 -p $PORT` 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 and a second, published bucket for public assets (`CDN_*`)
- An Ample account token with `servers:write`, `databases:read`, `buckets:read`

## Workflow Steps
1. **Build and start**  
   `next build` then `next start -H 0.0.0.0 -p $PORT` 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**  
   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.  
   `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`.  
   `ample logs --kind build`

## Success Checks
- App responds on its public URL
- Public-media-library self-test

## Limitations
- Verified on the node-22 template at `s-1vcpu-1gb` with the example fixture; other sizes, templates and Next.js 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.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- 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.00
- Authoritative: true
- Basis: size prices from `pricing.toml` (loaded by the API)

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

## Evidence Summary
- Next.js pattern fixture deployed on Ample; checks passed for public-media-library and configuration-secrets. 
- The same Next.js app deployed with a `--release-command` migration; the marker it created was readable after activation.
