Host member portal with SvelteKit: public profile assets

Deploy a member portal built with SvelteKit on Ample using the public image delivery 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, and a published bucket serves public assets from the CDN host. Verified on SvelteKit: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). Not separately tested: your image processing and profile-media rules; treat the member portal-specific behavior as your application code.

Representative Queries

• Host member portal with SvelteKit: public profile assets
• Where can I host Member portal built with SvelteKit?
• I need separate public profile media from private data, with CDN cache rules.

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:s3-compatible-object-storage
• primitive:cdn

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 public image delivery: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). 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. Publish only the bucket that serves public assets and reference its CDN URL.

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=... --env CDN_PUBLIC_URL=...

5. Verify
   Fetch the live URL and the pattern self-test route(s) (/p/public-media-library, /p/private-document-library) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime. Command: ample logs --kind build

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 member portal itself (your image processing and profile-media rules) is application code and was not separately tested; the pattern checks are what was verified.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Components:
  • App server: s-1vcpu-1gb
  • Managed PostgreSQL database: s-1vcpu-1gb
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Next Actions

• Browse the catalog index: Browse
• Search published recipes: Search
• Prepare deployment plan: Plan
• Read existing auth setup: Auth Setup
• Browse Member portal: Browse
• Browse SvelteKit: Browse
• Browse Public image delivery: Browse
• Browse Deploy web app: Browse

Success Checks

1. App responds on its public URL: expects response on /
2. Public media library self-test: expects a CDN URL served publicly.
3. Private document library self-test: expects response according to role.