# Host admin dashboard with SvelteKit: public profile assets

Deploy a admin dashboard built with SvelteKit on Ample using the public image delivery 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: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). Not separately tested: your image processing and profile-media rules; treat the admin dashboard-specific behavior as your application code.

## Representative Queries
- Host admin dashboard with SvelteKit: public profile assets
- Where can I host Admin dashboard built with SvelteKit?
- I need separate public profile media from private data, with CDN cache rules.

## Resource Requirements
- Compute
- PostgreSQL
- S3-compatible object storage
- CDN

## Infrastructure Requirements
### Compute
- **Summary**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

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

### S3-compatible Object Storage
- **Summary**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

### CDN
- **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 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 image delivery: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). 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, /p/private-document-library) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Components**:
  - app server: size s-1vcpu-1gb (quantity 1.0, monthlyAmount 5.0)
  - managed PostgreSQL database: size s-1vcpu-1gb (quantity 1.0, monthlyAmount 5.0)

## 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 admin dashboard itself (your image processing and profile-media 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.

## Next Actions
1. **Browse the catalog index**: [GET /v1/catalog](https://api.ample.computer/v1/catalog)
2. **Search published recipes by intent, stack and constraints**: [POST /v1/catalog/search](https://api.ample.computer/v1/catalog/search)
3. **Prepare a side-effect-free deployment plan for an authorized project**: [POST /v1/catalog/plan](https://api.ample.computer/v1/catalog/plan)
4. **Read the existing agent authentication setup**: [GET /mcp/setup](https://api.ample.computer/mcp/setup)
5. **Browse Admin dashboard**: [GET /v1/catalog/nodes/workload%3Aadmin-dashboard](https://api.ample.computer/v1/catalog/nodes/workload%3Aadmin-dashboard)
6. **Browse SvelteKit**: [GET /v1/catalog/nodes/stack%3Aframework-sveltekit](https://api.ample.computer/v1/catalog/nodes/stack%3Aframework-sveltekit)