# Host blog with SvelteKit: public-site delivery

Deploy a blog 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 blog-specific behavior as your application code.

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

## Resource Requirements
- **Primitive: Compute**
- **Primitive: CDN**

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

## Framework
**SvelteKit**

## Workload
**Blog**

## Prerequisites
1. 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).
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**: 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.
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`.

## Success Checks
- App responds on its public URL (kind: http_get, path: /, expect: ample canary sveltekit patterns)
- Versioned-static-assets self-test (kind: http_get, path: /p/versioned-static-assets, expect: a CDN URL whose content is served publicly)

## Limitations
- Verified on the node-22 template at s-1vcpu-1gb with the example fixture; other sizes, templates, and SvelteKit major versions are not verified.
- The blog 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.
- **Components**: 
  - **App server**: size: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0.
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

## Formats
- **HTML**: [Host blog with SvelteKit: public-site delivery](/content/recipes/blog/sveltekit/public-site/index.html)
- **Markdown**: [Host blog with SvelteKit: public-site delivery](/content/recipes/blog/sveltekit/public-site.md)
- **JSON**: [Host blog with SvelteKit: public-site delivery](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Ablog%3Asveltekit%3Apublic-site)