### Host campaign site with Next.js: public-site delivery

Deploy a campaign site built with Next.js on Ample using the public web service pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, and a published bucket serves public assets from the CDN host. Verified on Next.js: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL. Not separately tested: your site content and build; treat the campaign site-specific behavior as your application code.

#### Representative Queries
- Host campaign site with Next.js: public-site delivery
- Where can I host Campaign site built with Next.js?
- I need an explicit origin-to-CDN delivery path and a tested public content build.

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

#### Infrastructure Requirements
1. **Compute**
   - Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

2. **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 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 bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables
- An Ample account token with servers:write, 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. **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.

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.  
   `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=...`

4. **Verify**  
   Fetch the live URL and the pattern self-test route(s) (/p/versioned-static-assets) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.  
   `ample logs  --kind build`

#### 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 campaign site itself (your site content and build) is application code and was not separately tested; the pattern checks are what was verified.
- Other limitations on regional availability and compliance attestations.

#### Cost Estimate
- **Currency**: USD  
- **Monthly Amount**: 5.0  
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

#### Examples
- **Next.js pattern fixture**: Multi-pattern Next.js app whose public web service module was checked live; the module is under `tests/deploy-canaries/_pattern-modules`.

#### Success Checks
1. App responds on its public URL: 
   - **Path**: `/`  
   - **Expect**: `ample canary next js patterns`

2. Versioned-static-assets self-test: 
   - **Path**: `/p/versioned-static-assets`  
   - **Expect**: `a CDN URL whose content is served publicly`.