# Host product catalog with SvelteKit: inventory imports

Deploy a product catalog 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 product catalog-specific behavior as your application code.

## Representative Queries
- Host product catalog with SvelteKit: inventory imports
- Where can I host Product catalog built with SvelteKit?
- I need an inventory import contract, staging objects and row-level error handling.

## Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage

## 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.  
   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/bulk-import-staging) 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
- 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.
- The product catalog itself (your import format, mapping and conflict rules) is application code and was not separately tested; the pattern checks are what was verified.

## Cost Estimate
- **Monthly Amount**: $10.00
- **Basis**: Size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
     - App server (s-1vcpu-1gb): $5.00
     - Managed PostgreSQL database (s-1vcpu-1gb): $5.00

## Next Actions
- **[Browse the catalog index](https://api.ample.computer/v1/catalog)**
- **[Search published recipes by intent, stack and constraints](https://api.ample.computer/v1/catalog/search)**
- **[Prepare a side-effect-free deployment plan](https://api.ample.computer/v1/catalog/plan)**