page:recipes:product catalog:sveltekit:download delivery

Host product catalog with SvelteKit: authorized file delivery

Deploy a product catalog built with SvelteKit on Ample using the generated downloads 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: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Not separately tested: your export formats, retention policy and entitlement model; treat the product catalog-specific behavior as your application code.

Representative Queries

Resource Requirements

Infrastructure Requirements

Compute

Postgres

S3-compatible object storage

Prerequisites

  1. 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)
  2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
  3. A bucket from ample bucket create with its credentials passed as encrypted S3_* environment variables
  4. An Ample account token with servers:write, databases:read, buckets:read

Tested Configuration

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 generated downloads: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). 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/generated-downloads) 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. Description: app responds on its public URL
    Kind: http_get
    Path: /
    Expect: ample canary sveltekit patterns

  2. Description: generated-downloads self-test
    Kind: http_get
    Path: /p/generated-downloads
    Expect: export=ok rows=3 (with ?token=...; 401 without)

Limitations

Cost Estimate

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 generated-downloads and configuration-secrets. Pattern proof: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3).
    Observed At: 2026-09-20T03:31:44Z
    Implementation Revision: 03b6402b1b3e19178985f08ea4033804521d85d4-dirty (CLI b75e104)
    Expires At: 2027-03-19T03: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
    Implementation Revision: 199ff1dfd52683832ae75d3f98b53a7a4bff7f96-dirty (CLI e3181f5)
    Expires At: 2027-03-19T02:16:51Z

Unknowns

Formats

Next Actions

  1. Browse the catalog index

    • Action ID: browse-catalog
    • Operation ID: catalog_index
    • Method: GET
    • Relative Path: /v1/catalog

  2. Search published recipes by intent, stack and constraints

    • Action ID: search-recipes
    • Operation ID: search_recipes
    • Method: POST
    • Relative Path: /v1/catalog/search
    • Parameters: {"body":{"limit":5,"query":"Host product catalog with SvelteKit: authorized file delivery"}}

  3. Prepare a side-effect-free deployment plan for an authorized project

    • Action ID: plan:page:recipes:product-catalog:sveltekit:download-delivery
    • Operation ID: plan_deployment
    • Method: POST
    • Relative Path: /v1/catalog/plan
    • Parameters: {"body":{"inputs":{},"projectId":"","recipeId":"page:recipes:product-catalog:sveltekit:download-delivery","recipeRevision":"r1"}}

  4. Read the existing agent authentication setup

    • Action ID: auth-setup
    • Operation ID: existing_auth_setup
    • Method: GET
    • Relative Path: /mcp/setup

  5. Browse Product catalog

    • Action ID: browse:workload:product-catalog
    • Operation ID: browse_node
    • Method: GET
    • Relative Path: /v1/catalog/nodes/workload%3Aproduct-catalog

  6. Browse SvelteKit

    • Action ID: browse:stack:framework-sveltekit
    • Operation ID: browse_node
    • Method: GET
    • Relative Path: /v1/catalog/nodes/stack%3Aframework-sveltekit

  7. Browse Generated downloads

    • Action ID: browse:pattern:generated-downloads
    • Operation ID: browse_node
    • Method: GET
    • Relative Path: /v1/catalog/nodes/pattern%3Agenerated-downloads

  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