page:recipes:company website:sveltekit:public site

Host company website with SvelteKit: public-site delivery

Deploy a company website built with SvelteKit on Ample using the public web service pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, and a published bucket serves public assets from the CDN host. Verified on SvelteKit: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL. Not separately tested: your site content and build; treat the company website-specific behavior as your application code.

Summary

Workflow Steps

  1. Build and start: Run 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. 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. Publish only the bucket that serves public assets and reference its CDN URL.
  3. 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.
    ample deploy . --name  --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=...
    
  4. Verify: Fetch the live URL and the pattern self-test route(s) (/p/versioned-static-assets); then run your own checks. On failure read ample logs --kind build then --kind runtime.
    ample logs --kind build
    

Limitations

Cost Estimate

Examples

Next Actions

  1. Browse Catalog: View the catalog index.
  2. Search Recipes: Search published recipes by intent, stack, and constraints.
  3. Prepare Deployment Plan: Plan for an authorized project.