page:recipes:reporting dashboard:sveltekit:attachments

Host reporting dashboard with SvelteKit: file attachments

Deploy a reporting dashboard built with SvelteKit on Ample using the browser file uploads 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: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok). Not separately tested: your upload UI, allowed types, size limits and virus scanning; treat the reporting dashboard-specific behavior as your application code.

Representative Queries

• Host reporting dashboard with SvelteKit: file attachments
• Where can I host Reporting dashboard built with SvelteKit?
• I need a restricted upload flow, file validation and record-to-object linkage.

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.
• 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 browser file uploads: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key.
3. Wire object storage: Create the bucket(s), then pass endpoint, region, bucket and keys as --env values.
4. Deploy: Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked).
5. Verify: Fetch the live URL and the pattern self-test route(s) (/p/browser-file-uploads) from the example; then run your own checks.

Success Checks

• App responds on its public URL.
• Browser-file-uploads 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 reporting dashboard itself (your upload UI, allowed types, size limits and virus scanning) is application code and was not separately tested.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Components:
  • App server (s-1vcpu-1gb): 5.0
  • Managed PostgreSQL database (s-1vcpu-1gb): 5.0

Evidence Summary

• SvelteKit pattern fixture deployed on Ample; checks passed for browser-file-uploads and configuration-secrets.

Formats

• HTML: HTML Representation
• Markdown: Markdown Representation
• JSON: JSON Representation

Next Actions

1. Browse the catalog index
2. Search published recipes by intent, stack and constraints
3. Prepare a side-effect-free deployment plan for an authorized project.