# Host Partner Portal with SvelteKit: Application Activity History

Deploy a partner portal built with SvelteKit on Ample using the transactional workflows 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`. Verified on SvelteKit: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (`history=2 conflict=rejected`). Not separately tested: your domain records, validation rules and concurrency policy; treat the partner portal-specific behavior as your application code.

## Summary of Representative Queries
- Host partner portal with SvelteKit: application activity history
- Where can I host Partner portal built with SvelteKit?
- I need an application-owned event schema and tested history queries; not native platform audit logs.

## Resource Requirements
- **Compute**
- **Postgres**

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

## 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)
- An Ample account token with `servers:write`, `databases: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**  
   - Body: 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**  
   - Body: The fixture's module implements transactional workflows: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

3. **Deploy**  
   - Body: 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`

4. **Verify**  
   - Body: Fetch the live URL and the pattern self-test route(s) (/p/transactional-workflows) from the example; then run your own checks. On failure read `ample logs --kind build` then `--kind runtime`.  
   - Command: `ample logs --kind build`

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

2. Transactional workflows self-test  
   - Kind: http_get  
   - Path: /p/transactional-workflows  
   - Expect: `tx=ok history=2 conflict=rejected`

## 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 domain records, validation rules, and concurrency 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.

## Cost Estimate
- **Currency**: USD  
- **Monthly Amount**: 10.0  
- **Authoritative**: true  
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
  - **Components**:  
     - App Server (size: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0)  
     - Managed PostgreSQL Database (size: s-1vcpu-1gb, quantity: 1.0, 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.

## Evidence Summary
- **Canary Run:** SvelteKit pattern fixture deployed on Ample; checks passed for transactional workflows and configuration secrets. 
- **Observed At**: 2026-09-20T03:31:44Z
- **Last Verified At**: 2026-09-20T03:31:44Z

## Next Actions
1. **Action ID**: browse-catalog  
   - Label: Browse the catalog index  
   - Method: GET  
   - Relative Path: /v1/catalog

2. **Action ID**: search-recipes  
   - Label: Search published recipes by intent, stack, and constraints  
   - Method: POST  
   - Relative Path: /v1/catalog/search
