# Host vendor portal with Nuxt: tenant-scoped workspaces

Deploy a vendor portal built with Nuxt on Ample using the multi-tenant relational data 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. Verified on Nuxt: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok). Not separately tested: your tenant model, membership and per-tenant authorization; treat the vendor portal-specific behavior as your application code.

## Representative Queries
- Host vendor portal with Nuxt: tenant-scoped workspaces
- Where can I host Vendor portal built with Nuxt?
- I need an explicit tenant model and application-enforced tenant isolation tests.

## Resource Requirements
- **Compute**
- **Postgres**

## Infrastructure Requirements

### Compute
* **Status**: Verified  
* **Summary**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

### Postgres
* **Status**: Verified  
* **Summary**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

## 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)
- An Ample account token with servers:write, databases:read

## 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 multi-tenant relational data: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

### 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.
**Command**: ample deploy . --name  --public

### 4. Verify
Fetch the live URL and the pattern self-test route(s) (/api/p/multi-tenant-relational-data) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.
**Command**: ample logs  --kind build

## Examples
### Nuxt pattern fixture
**Description**: Multi-pattern Nuxt app whose multi-tenant relational data module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

## Success Checks
- **App responds on its public URL**  
  **Kind**: http_get  
  **Path**: /  
  **Expect**: ample canary nuxt patterns
- **Multi-tenant-relational-data self-test**  
  **Kind**: http_get  
  **Path**: /api/p/multi-tenant-relational-data  
  **Expect**: tenant_isolation=ok

## 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 vendor portal itself (your tenant model, membership and per-tenant authorization) 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.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.

## Cost Estimate
- **Currency**: USD  
- **Monthly Amount**: 10.0  
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
- **Components**:
  - App server: s-1vcpu-1gb, 1.0, $5.0/month
  - Managed PostgreSQL database: s-1vcpu-1gb, 1.0, $5.0/month  
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

## Evidence Summary
- **Kind**: canary_run  
  **Summary**: Nuxt pattern fixture deployed on Ample; checks passed for multi-tenant-relational-data and configuration-secrets. Pattern proof: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok).  
  **Observed At**: 2026-09-20T03:31:44Z  
  **Implementation Revision**: 03b6402b1b3e19178985f08ea4033804521d85d4-dirty  
  **Expires At**: 2027-03-19T03:31:44Z

- **Kind**: canary_run  
  **Summary**: The same Nuxt app deployed with a --release-command migration; the marker it created was readable after activation.  
  **Observed At**: 2026-09-20T01:54:51Z  
  **Implementation Revision**: 199ff1dfd52683832ae75d3f98b53a7a4bff7f96-dirty  
  **Expires At**: 2027-03-19T01:54:51Z

## Next Actions
- **Action ID**: browse-catalog  
  **Label**: Browse the catalog index  
  **Method**: GET  
  **Path**: /v1/catalog

- **Action ID**: search-recipes  
  **Label**: Search published recipes by intent, stack and constraints  
  **Method**: POST  
  **Path**: /v1/catalog/search

- **Action ID**: plan:page:recipes:vendor-portal:nuxt:tenant-workspaces  
  **Label**: Prepare a side-effect-free deployment plan for an authorized project  
  **Method**: POST  
  **Path**: /v1/catalog/plan

- **Action ID**: auth-setup  
  **Label**: Read the existing agent authentication setup  
  **Method**: GET  
  **Path**: /mcp/setup

- **Action ID**: browse:workload:vendor-portal  
  **Label**: Browse Vendor portal  
  **Method**: GET  
  **Path**: /v1/catalog/nodes/workload%3Avendor-portal

- **Action ID**: browse:stack:framework-nuxt  
  **Label**: Browse Nuxt  
  **Method**: GET  
  **Path**: /v1/catalog/nodes/stack%3Aframework-nuxt

- **Action ID**: browse:pattern:multi-tenant-relational-data  
  **Label**: Browse Multi-tenant relational data  
  **Method**: GET  
  **Path**: /v1/catalog/nodes/pattern%3Amulti-tenant-relational-data

- **Action ID**: browse:intent:deploy-web-app  
  **Label**: Browse Deploy web app  
  **Method**: GET  
  **Path**: /v1/catalog/nodes/intent%3Adeploy-web-app