# Host marketplace with SvelteKit: public product media

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

## Representative Queries
- Host marketplace with SvelteKit: public product media
- Where can I host Marketplace 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
- **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- **Postgres**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
- **S3-compatible object storage**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.
- **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
**Marketplace**

## Release Status
**Published**

## Support Status
**Verified**

## Execution Status
**Ready**

## 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 and a second, published bucket for public assets (CDN_*)
- 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 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.
   ```bash
   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/public-media-library) from the example; then run your own checks. On failure read `ample logs --kind build` then `--kind runtime`.
   ```bash
   ample logs --kind build
   ```

## 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.
   Source: tests/deploy-canaries/sveltekit-patterns

## Success Checks
- app responds on its public URL (HTTP GET path: /) expecting: ample canary sveltekit patterns
- public-media-library self-test (HTTP GET path: /p/public-media-library) expecting: 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 marketplace itself (your media processing, object layout and cache policy) is application code and was not separately tested; the pattern checks are what was verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.
- PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not.
- The CDN serves published-bucket objects only; cache rules, purge and TTL control are not verified (the fixture sets Cache-Control on upload and versions keys).

## Cost Estimate
- **Monthly Amount**: $10.00 USD (authoritative)
- **Basis**: Size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty

### Components
- App server: s-1vcpu-1gb, quantity: 1.0, monthly amount: $5.00
- Managed PostgreSQL database: s-1vcpu-1gb, quantity: 1.0, monthly amount: $5.00

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

## Next Actions
- **Browse the catalog index**: Browse the catalog index.  
  Operation ID: catalog_index  
  Method: GET  
  Relative Path: /v1/catalog  
- **Search published recipes by intent, stack and constraints**: Search published recipes for a specific query.  
  Operation ID: search_recipes  
  Method: POST  
  Relative Path: /v1/catalog/search  
- **Prepare a side-effect-free deployment plan for an authorized project**: Prepare a deployment plan.  
  Operation ID: plan_deployment  
  Method: POST  
  Relative Path: /v1/catalog/plan

---

Formats:  
- [HTML Format](/content/recipes/marketplace/sveltekit/product-media/index.html)  
- [Markdown Format](/content/recipes/marketplace/sveltekit/product-media.md)  
- [JSON Format](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Amarketplace%3Asveltekit%3Aproduct-media)