# Host event registration with SvelteKit: data exports

Deploy an event registration built with SvelteKit on Ample using the generated downloads 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: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Not separately tested: your export formats, retention policy and entitlement model; treat the event registration-specific behavior as your application code.

## Representative Queries
- Host event registration with SvelteKit: data exports
- Where can I host Event registration built with SvelteKit?
- I need a scoped export format, artifact generation and authorized download procedure.

## Resource Requirements
- Compute
- Postgres
- S3-compatible object storage

## Infrastructure Requirements
1. **Compute**: 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**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
3. **S3-compatible object storage**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

## 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
- 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 generated downloads: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). 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.
5. **Verify**: Fetch the live URL and the pattern self-test route(s) (/p/generated-downloads) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.

## Examples
- **SvelteKit pattern fixture**: Multi-pattern SvelteKit app whose generated downloads module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

## Success Checks
1. App responds on its public URL (expect: ample canary sveltekit patterns).
2. Generated-downloads self-test (expect: export=ok rows=3).

## 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 event registration itself (your export formats, retention policy and entitlement model) is application code and was not separately tested; the pattern checks are what was verified.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
- Components:
  - **App server**: s-1vcpu-1gb; monthly amount: 5.0
  - **Managed PostgreSQL database**: s-1vcpu-1gb; monthly amount: 5.0

## Next Actions
- **Browse the catalog index**: GET /v1/catalog
- **Search published recipes**: POST /v1/catalog/search
- **Prepare a deployment plan**: POST /v1/catalog/plan
- **Read existing authentication setup**: GET /mcp/setup
- **Browse Event registration**: GET /v1/catalog/nodes/workload%3Aevent-registration
- **Browse SvelteKit**: GET /v1/catalog/nodes/stack%3Aframework-sveltekit
- **Browse Generated downloads**: GET /v1/catalog/nodes/pattern%3Agenerated-downloads
- **Browse Deploy web app**: GET /v1/catalog/nodes/intent%3Adeploy-web-app