### Host partner portal with Nuxt: tenant-scoped workspaces

Deploy a partner 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 partner portal-specific behavior as your application code.

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

#### Resource Requirements
- primitive:compute
- primitive:postgres

#### Infrastructure Requirements
- **Compute**  \(verified\) \- Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- **Postgres**  \(verified\) \- 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

#### Workflow Steps
1. **Build and start**\n   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**\n   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**\n   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.\n   `ample deploy . --name  --public`
4. **Verify**\n   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`.\n   `ample logs  --kind build`

#### Examples
- **Nuxt pattern fixture**  \- 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**  \(http_get\) \- `/`, expect: `ample canary nuxt patterns`
- **Multi-tenant-relational-data self-test**  \(http_get\) \- `/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 partner 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.

#### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0

Components:
- App Server \(size: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0\)
- Managed PostgreSQL Database \(size: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 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 multi-tenant-relational-data and configuration-secrets. Pattern proof: a tenant column on every row and query, with a cross-tenant read returning nothing.

#### Next Actions
- **Browse the catalog index**  \- `GET /v1/catalog`
- **Search published recipes**  \- `POST /v1/catalog/search`
- **Prepare a side-effect-free deployment plan**  \- `POST /v1/catalog/plan`
- **Read the existing agent authentication setup**  \- `GET /mcp/setup` 
- **Browse Partner portal**  \- `GET /v1/catalog/nodes/workload%3Apartner-portal`
- **Browse Nuxt**  \- `GET /v1/catalog/nodes/stack%3Aframework-nuxt`
- **Browse Multi-tenant relational data**  \- `GET /v1/catalog/nodes/pattern%3Amulti-tenant-relational-data`
- **Browse Deploy web app**  \- `GET /v1/catalog/nodes/intent%3Adeploy-web-app`