Host member portal with Nuxt: public profile assets

Deploy a member portal 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). 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 Nuxt: public profile assets
• Where can I host Member portal built with Nuxt?
• 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

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.
4. CDN: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

Prerequisites

• A Nuxt project that builds and starts with the documented commands (nuxt build then node .output/server/index.mjs (reads HOST and PORT) on the node-22 template)
• A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
• A bucket from ample bucket create with its credentials passed as encrypted S3_* environment variables and a second, published bucket for public assets (CDN_*)
• An Ample account token with servers:write, databases:read, buckets:read

Workflow 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: 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.
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 run your own checks.

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.

Limitations

• Verified on the node-22 template; other sizes, templates and Nuxt major versions are not verified.
• The member portal itself is application code and was not separately tested; the pattern checks are what was verified.

Cost Estimate

• Monthly Amount: 10.0 USD
• Components:
  • App server: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0
  • Managed PostgreSQL database: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0

Next Actions

• Browse the catalog index: GET /v1/catalog
• Search published recipes: POST /v1/catalog/search
• Prepare deployment plan: POST /v1/catalog/plan
• Read existing agent authentication setup: GET /mcp/setup
• Browse Member portal: GET /v1/catalog/nodes/workload%3Amember-portal
• Browse Nuxt: GET /v1/catalog/nodes/stack%3Aframework-nuxt
• Browse Public image delivery: GET /v1/catalog/nodes/pattern%3Apublic-image-delivery
• Browse Deploy web app: GET /v1/catalog/nodes/intent%3Adeploy-web-app