### Host product catalog with SvelteKit: public product media

Deploy a product catalog built with SvelteKit on Ample using the public media library 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, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables, and a published bucket serves public assets from the CDN host. Verified on SvelteKit: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. Not separately tested: your media processing, object layout and cache policy; treat the product catalog-specific behavior as your application code.

#### Representative Queries
- Host product catalog with SvelteKit: public product media
- Where can I host Product catalog built with SvelteKit?
- I need product-to-object mappings and a tested public media delivery path.

#### Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage
- 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. **S3-compatible object storage**
   - Status: verified
   - Summary: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.
4. **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.

#### 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. **Implement the pattern on PostgreSQL**  
The fixture's module implements public media library: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. 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.
5. **Verify**  
Fetch the live URL and the pattern self-test route(s) (/p/public-media-library) 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 media library module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

#### Success Checks
1. App responds on its public URL
2. Public-media-library self-test

#### 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 product catalog itself (your media processing, object layout and cache policy) 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
- Components:
  - App server: s-1vcpu-1gb
  - Managed PostgreSQL database: s-1vcpu-1gb
- Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

#### Next Actions
1. Browse the catalog index  
2. Search published recipes by intent, stack and constraints  
3. Prepare a side-effect-free deployment plan for an authorized project  
4. Read the existing agent authentication setup  
5. Browse Product catalog  
6. Browse SvelteKit  
7. Browse Public media library  
8. Browse Deploy web app