# Host partner portal with SvelteKit: private documents

### Summary
Deploy a partner 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).

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

### 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`

### Examples
- **SvelteKit pattern fixture**  
  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`

### Success Checks
- **app responds on its public URL**  
  Kind: `http_get`  
  Path: `/`  
  Expect: `ample canary sveltekit patterns`

- **private-document-library self-test**  
  Kind: `http_get`  
  Path: `/p/private-document-library`  
  Expect: `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 partner portal itself (your identity integration and role assignments) 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) - $5.0
  - Managed PostgreSQL database (s-1vcpu-1gb) - $5.0

### Evidence Summary
- **SvelteKit pattern fixture deployed on Ample**  
  Summary: Checks passed for private-document-library and configuration-secrets.
  Observed At: `2026-09-20T03:31:44Z`

### Next Actions
- **Browse the catalog index**: GET `/v1/catalog`
- **Search published recipes by intent, stack and constraints**: POST `/v1/catalog/search`
- **Prepare a side-effect-free deployment plan for an authorized project**: POST `/v1/catalog/plan`
- **Read the existing agent authentication setup**: GET `/mcp/setup`