### Host asset library with SvelteKit: structured data imports

Deploy a asset library built with SvelteKit on Ample using the bulk import staging 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 CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). Not separately tested: your import format, mapping and conflict rules; treat the asset library-specific behavior as your application code.

**Representative Queries**
- Host asset library with SvelteKit: structured data imports
- Where can I host Asset library built with SvelteKit?
- I need a workload-specific import mapping, conflict rules and restart behavior.

**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 bulk import staging: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=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.  
   
   `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/bulk-import-staging) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.  
   
   `ample logs  --kind build`

**Examples**
- **SvelteKit pattern fixture**  
  Multi-pattern SvelteKit app whose bulk import staging module was checked live; the module is under tests/deploy-canaries/_pattern-modules.  
  
   **Success Checks**  
   - App responds on its public URL
   - bulk-import-staging self-test

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

**Cost Estimate**  
- Monthly Amount: $10.00  
   - App server: size s-1vcpu-1gb  
   - Managed PostgreSQL database: size s-1vcpu-1gb

This is a summary of how to set up an asset library with SvelteKit. Make sure to adhere to the steps and verify the app properly.