# Host public directory with SvelteKit: public-site delivery

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

## Summary
- **Framework**: SvelteKit
- **Workload**: Public directory
- **Release Status**: published
- **Support Status**: verified
- **Execution Status**: ready

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

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

## Input Schema
- **env**: Encrypted environment variables (bucket credentials, secrets)
- **name**: App name
- **path**: Project directory or ample.toml service
- **release_command**: Migration command run before activation

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

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

## Success Checks
- app responds on its public URL: **http_get** on `/`, expect: ample canary sveltekit patterns
- versioned-static-assets self-test: **http_get** on `/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 public directory 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

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.