Host admin dashboard with Nuxt: private documents

Deploy a admin dashboard built with Nuxt on Ample using the private document library 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 Nuxt: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). Not separately tested: your identity integration and role assignments; treat the admin dashboard-specific behavior as your application code.

Representative Queries

• Host admin dashboard with Nuxt: private documents
• Where can I host Admin dashboard built with Nuxt?
• I need a role-to-document access model and negative authorization tests.

Resource Requirements

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

Infrastructure Requirements

• Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
• 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.
• S3-compatible object storage: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

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
   The fixture's module implements private document library: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). 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.
   ample deploy . --name <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) (/api/p/private-document-library) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.
   ample logs --kind build

Tested Configuration

• Template: node-22
• Runtime: node
• Size: s-1vcpu-1gb
• Install: npm install
• Build: npm run build --if-present
• Start: npm run start

Examples

• Nuxt pattern fixture: Multi-pattern Nuxt app whose private document library module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

Success Checks

• HTTP GET: app responds on its public URL
• HTTP GET: private-document-library self-test
  (expect: private=ok (with ?role=owner; 401 without, 403 for viewer))

Limitations

• Verified on the node-22 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Nuxt major versions are not verified.
• The admin dashboard itself (your identity integration and role assignments) is application code and was not separately tested; the pattern checks are what was verified.
• Region, compliance attestations and request-duration limits are unknown and not claimed.

Cost Estimate

• Monthly Amount: 10.0 USD
  • App Server: Size: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0
  • Managed PostgreSQL Database: Size: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0
    Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Evidence Summary

• Canary Run: Nuxt pattern fixture deployed on Ample; checks passed for private-document-library and configuration-secrets.
• Canary Run: The same Nuxt app deployed with a --release-command migration; the marker it created was readable after activation.

Next Actions

• Browse catalog index
  • Operation ID: catalog_index
• Search published recipes
  • Operation ID: search_recipes
• Prepare a deployment plan
  • Operation ID: plan_deployment
• Read existing authentication setup
  • Operation ID: existing_auth_setup
• Browse Admin dashboard
  • Operation ID: browse_node
• Browse Nuxt
  • Operation ID: browse_node
• Browse Private document library
  • Operation ID: browse_node
• Browse Deploy web app
  • Operation ID: browse_node