# Host blog with SvelteKit: Postgres-backed content

Deploy a blog built with SvelteKit on Ample using the relational records pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL, and a published bucket serves public assets from the CDN host. Verified on SvelteKit: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Not separately tested: your record schema, states and access rules; treat the blog-specific behavior as your application code.

## Representative Queries
- Host blog with SvelteKit: Postgres-backed content
- Where can I host Blog built with SvelteKit?
- I need a content schema, publishing workflow and cache behavior after content updates.

## Resource Requirements
- primitive:compute
- primitive:postgres
- 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. **Postgres**
   - **Status**: verified
   - **Summary**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
3. **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.

## 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 PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
- A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables
- An Ample account token with servers:write, databases:read, 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. **Implement the pattern on PostgreSQL**  
The fixture's module implements relational records: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. **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.
4. **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=...`
5. **Verify**  
Fetch the live URL and the pattern self-test route(s) (/p/relational-records) from the example; then run your own checks. On failure read `ample logs --kind build` then `--kind runtime`.  
   `ample logs --kind build`

## Success Checks
- app responds on its public URL
- relational-records self-test using HTTP GET at path /p/relational-records

## 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 record schema, states and access rules) is application code and was not separately tested; the pattern checks are what was verified.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
   - **Components**:
     1. app server: size `s-1vcpu-1gb`, quantity 1.0, monthly amount 5.0
     2. managed PostgreSQL database: size `s-1vcpu-1gb`, quantity 1.0, monthly amount 5.0
- **Note**: Always-on monthly price of the tested sizes.

## Evidence Summary
- **SvelteKit pattern fixture** deployed on Ample; checks passed for relational-records and configuration-secrets.

## Last Verified At
- 2026-09-20T03:31:44Z

## Formats
- [HTML](/content/recipes/blog/sveltekit/relational-content/index.html)
- [Markdown](/content/recipes/blog/sveltekit/relational-content.md)
- [JSON](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Ablog%3Asveltekit%3Arelational-content)