page:recipes:csv import tool:sveltekit:data imports
Host csv import tool with SvelteKit: structured data imports
Deploy a csv import tool 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 csv import tool-specific behavior as your application code.
Representative Queries
- Host csv import tool with SvelteKit: structured data imports
- Where can I host CSV import tool built with SvelteKit?
- I need a workload-specific import mapping, conflict rules and restart behavior.
Workflow Steps
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.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.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.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=...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 readample logs --kind buildthen--kind runtime.Command:
ample logs --kind build
Input Schema
{
"type": "object",
"additionalProperties": false,
"required": ["env", "name", "path"],
"properties": {
"env": {
"type": "array",
"items": {
"type": "string",
"pattern": "^[A-Z][A-Z0-9_]*=.*$"
},
"maxItems": 50,
"description": "Encrypted environment variables (bucket credentials, secrets)"
},
"name": {
"type": "string",
"minLength": 1,
"maxLength": 63,
"pattern": "^[a-z0-9-]+$",
"description": "App name"
},
"path": {
"type": "string",
"minLength": 1,
"maxLength": 512,
"description": "Project directory or ample.toml service"
},
"release_command": {
"type": "string",
"maxLength": 512,
"description": "Migration command run before activation"
}
}
}
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 csv import tool 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
- Currency: USD
- Monthly Amount: $10.00
- Components:
- App server (s-1vcpu-1gb): $5.00
- Managed PostgreSQL database (s-1vcpu-1gb): $5.00
Success Checks
- App responds on its public URL (kind: http_get, path: /, expect: ample canary sveltekit patterns)
- Bulk-import-staging self-test (kind: http_get, path: /p/bulk-import-staging, expect: imported=2 rejected=1 restart=ok)
Evidence Summary
- Canary Run: SvelteKit pattern fixture deployed on Ample; checks passed for bulk-import-staging and configuration-secrets.
- Last Verified At: 2026-09-20T03:31:44Z
Next Actions
- Browse the catalog index
- Search published recipes by intent, stack and constraints
- Prepare a side-effect-free deployment plan for an authorized project
- Read the existing agent authentication setup
- Browse CSV import tool
- Browse SvelteKit
- Browse Bulk import staging
- Browse Deploy web app
For further details, refer to the SvelteKit deployment documentation.