Host community forum with Nuxt: public profile assets · Ample Computer

Host community forum with Nuxt: public profile assets

Deploy a community forum built with Nuxt 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 Nuxt: 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). The community forum-specific behavior (your image processing and profile-media rules) is your application code on that verified basis.

What it runs on

You need

Exact tested configuration

build

npm run build --if-present

install

npm install

runtime

node

sizes-1vcpu-1gb

start

npm run start

template node-22

Steps

  1. Build and start. nuxt build then node .output/server/index.mjs (reads HOST and PORT) 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 needs an answer first). Re-running with no change is a no-op.

    ample deploy . --name <app-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) (/api/p/public-media-library, /api/p/private-document-library) from the example; then run your own checks. On failure read `ample logs <deployment_id> --kind build` then `--kind runtime`.

```bash
    ample logs <deployment_id> --kind build
    ```

## How it was checked

✓ app responds on its public URL· http get/ → “ample canary nuxt patterns”  
✓ public-media-library self-test· http get/api/p/public-media-library → “a CDN URL whose content is served publicly”  
✓ private-document-library self-test· http get/api/p/private-document-library → “private=ok (with ?role=owner; 401 without, 403 for viewer)”

## Evidence

1. November 6, 2026 · canary run  
Nuxt pattern fixture deployed on Ample (nuxt build then node .output/server/index.mjs (reads HOST and PORT) on the node-22 template); checks passed for public-media-library, private-document-library and configuration-secrets. Pattern proof: 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).

2. November 5, 2026 · canary run  
The same Nuxt app deployed with a --release-command migration; the marker it created was readable after activation.

## Tested examples

- **Nuxt pattern fixture.** Multi-pattern Nuxt app whose public image delivery module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

## What it doesn’t cover

- Verified on the node-22 template at s-1vcpu-1gb with the example fixture.

- The pattern checks verified the platform side; the community forum itself (your image processing and profile-media rules) is your application code.

- Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.

- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture); `ample bucket upload-url` returns presigned upload URLs.

- The CDN serves published-bucket objects; control caching with Cache-Control on upload and versioned keys.