## Host public directory with SvelteKit: bulk content imports

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

### Representative Queries
- Host public directory with SvelteKit: bulk content imports
- Where can I host Public directory built with SvelteKit?
- I need a staged import format, validation procedure and import recovery workflow.

### Resource Requirements
- `primitive:compute`
- `primitive:postgres`
- `primitive: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 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
1. **App responds on its public URL**:
   - Kind: http_get  
   - Path: /  
   - Expect: ample canary sveltekit patterns
2. **Bulk-import-staging self-test**:
   - Kind: http_get  
   - Path: /p/bulk-import-staging  
   - Expect: imported=2 rejected=1 restart=ok

### 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 public directory itself (your import format, mapping and conflict rules) 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.
- PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not.

### 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, monthlyAmount: 5.0
  - Managed PostgreSQL database: size: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 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
1. **Canary run**: SvelteKit pattern fixture deployed on Ample (vite build with @sveltejs/adapter-node then node build on the node-22 template); checks passed for bulk-import-staging and configuration-secrets. Pattern proof: 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).
   - Observed At: 2026-09-20T03:31:44Z
2. **Canary run**: The same SvelteKit app deployed with a --release-command migration; the marker it created was readable after activation.
   - Observed At: 2026-09-20T02:16:51Z

### Next Actions
1. **Browse the catalog index**  
   - Action ID: browse-catalog
   - Operation ID: catalog_index
   - Method: GET
   - Relative Path: /v1/catalog
   - Requires Authentication: false

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

3. **Prepare a side-effect-free deployment plan for an authorized project**  
   - Action ID: plan:page:recipes:public-directory:sveltekit:content-imports
   - Operation ID: plan_deployment
   - Method: POST
   - Relative Path: /v1/catalog/plan  
   - Requires Authentication: true

4. **Read the existing agent authentication setup**  
   - Action ID: auth-setup
   - Operation ID: existing_auth_setup
   - Method: GET
   - Relative Path: /mcp/setup
   - Requires Authentication: false

5. **Browse Public directory**  
   - Action ID: browse:workload:public-directory
   - Operation ID: browse_node
   - Method: GET
   - Relative Path: /v1/catalog/nodes/workload%3Apublic-directory
   - Requires Authentication: false

6. **Browse SvelteKit**  
   - Action ID: browse:stack:framework-sveltekit
   - Operation ID: browse_node
   - Method: GET
   - Relative Path: /v1/catalog/nodes/stack%3Aframework-sveltekit
   - Requires Authentication: false

7. **Browse Bulk import staging**  
   - Action ID: browse:pattern:bulk-import-staging
   - Operation ID: browse_node
   - Method: GET
   - Relative Path: /v1/catalog/nodes/pattern%3Abulk-import-staging
   - Requires Authentication: false

8. **Browse Deploy web app**  
   - Action ID: browse:intent:deploy-web-app
   - Operation ID: browse_node
   - Method: GET
   - Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app
   - Requires Authentication: false