### Host knowledge base with SvelteKit: public-site delivery

Deploy a knowledge base built with SvelteKit 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 SvelteKit: 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 knowledge base-specific behavior as your application code.

#### Representative Queries
- Host knowledge base with SvelteKit: public-site delivery
- Where can I host Knowledge base built with SvelteKit?
- I need an explicit origin-to-CDN delivery path and a tested public content build.

#### 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.
- **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 SvelteKit project that builds and starts with the documented commands (vite build with @sveltejs/adapter-node then node build 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**  
vite build with @sveltejs/adapter-node then node build 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.
   ```bash
   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`.
   ```bash
   ample logs  --kind build
   ```

### Output Schema
- **Format:** 
  - [Markdown](/content/recipes/knowledge-base/sveltekit/public-site.md)  
  - [HTML](/content/recipes/knowledge-base/sveltekit/public-site/index.html)  
  - [JSON](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Aknowledge-base%3Asveltekit%3Apublic-site)

### Cost Estimate
- **Currency:** USD  
- **Monthly Amount:** 5.0  
- **Basis:** size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty.
- **Note:** Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.