## Host knowledge base with Astro: public-site delivery  
Deploy a knowledge base built with Astro 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 Astro: 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 Astro: public-site delivery  
- Where can I host Knowledge base built with Astro?  
- 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**  
   - 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. **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.

### Framework
- **Astro**

### Workload
- **Knowledge base**

### Release Status
- **published**

### Support Status
- **verified**

### Execution Status
- **ready**

### Prerequisites
1. A Astro project that builds and starts with the documented commands (astro build with the @astrojs/node standalone adapter then node ./dist/server/entry.mjs on the node-22 template)  
2. A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables  
3. An Ample account token with servers:write, buckets:read

### Tested Configuration
- **Template**: node-22  
- **Runtime**: node  
- **Size**: s-1vcpu-1gb  
- **Install**: npm install  
- **Build**: npm run build --if-present  
- **Start**: npm run start

### Workflow Steps
1. **Build and start**  
   - astro build with the @astrojs/node standalone adapter then node ./dist/server/entry.mjs 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.
   - 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=...  
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`.
   - Command: ample logs  --kind build

### Success Checks
- App responds on its public URL  
- Versioned-static-assets self-test

### Limitations
- Verified on the node-22 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Astro major versions are not verified.  
- The knowledge base itself (your site content and build) is application code and was not separately tested; the pattern checks are what was verified.

### Cost Estimate
- **Currency**: USD  
- **Monthly Amount**: 5.0  
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty

### Evidence Summary
- # Astro pattern fixture deployed on Ample