### Host client portal with SvelteKit: private documents

Deploy a client portal built with SvelteKit on Ample using the private document 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. Verified on SvelteKit: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). Not separately tested: your identity integration and role assignments; treat the client portal-specific behavior as your application code.

### Summary
- **Family**: Workload recipe
- **Framework**: SvelteKit
- **Workload**: Client portal
- **Release Status**: published
- **Support Status**: verified
- **Execution Status**: ready
- **Docs Only**: false

### Representative Queries
- Host client portal with SvelteKit: private documents
- Where can I host Client portal built with SvelteKit?
- I need a role-to-document access model and negative authorization tests.

### Prerequisites
1. 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).
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env).
3. A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables.
4. An Ample account token with servers:write, databases:read, buckets:read.

### 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 private document library: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). 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.
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.
   - Command: `ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...`
5. **Verify**: Fetch the live URL and the pattern self-test route(s) (/p/private-document-library) from the example; then run your own checks. On failure read `ample logs --kind build` then `--kind runtime`.
   - Command: `ample logs --kind build`

### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Basis**: size prices from pricing.toml (loaded by the API)
- **Components**:
  - **App server**: size s-1vcpu-1gb - monthly amount 5.0
  - **Managed PostgreSQL database**: size s-1vcpu-1gb - monthly amount 5.0
- **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.

### Success Checks
1. **App responds on its public URL**: `http_get` on `/` expecting `ample canary sveltekit patterns`
2. **Private-document-library self-test**: `http_get` on `/p/private-document-library` expecting `private=ok (with ?role=owner; 401 without, 403 for viewer)`.

### 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 client portal itself (your identity integration and role assignments) 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.

### Examples
- **Title**: SvelteKit pattern fixture
  - **Description**: Multi-pattern SvelteKit app whose private document library module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
  - **Source Ref**: tests/deploy-canaries/sveltekit-patterns

### Evidence Summary
- **Kind**: canary_run, **Summary**: SvelteKit pattern fixture deployed on Ample; checks passed for private-document-library and configuration-secrets.
- **Kind**: canary_run, **Summary**: The same SvelteKit app deployed with a --release-command migration; the marker it created was readable after activation.