### Host admin dashboard with Nuxt: application activity history

**Summary**  
Deploy an admin dashboard built with Nuxt on Ample using the transactional workflows 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: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). Not separately tested: your domain records, validation rules and concurrency policy; treat the admin dashboard-specific behavior as your application code.

**Representative Queries**  
- Host admin dashboard with Nuxt: application activity history  
- Where can I host Admin dashboard built with Nuxt?  
- I need an application-owned event schema and tested history queries; not native platform audit logs.

---

### 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**  
   `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. **Deploy**  
   `ample deploy . --name  --public`  
4. **Verify**  
   `ample logs  --kind build`

### 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 domain records, validation rules and concurrency policy) is application code and was not separately tested; the pattern checks are what was verified.

### Examples  
- **Nuxt pattern fixture**  
   Multi-pattern Nuxt app whose transactional workflows module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

### Success Checks  
- **HTTP Get Check** on `/`: app responds on its public URL. Expect `ample canary nuxt patterns`.  
- **Transactional Workflows Check** on `/api/p/transactional-workflows`. Expect `tx=ok history=2 conflict=rejected`.
  
### Cost Estimate  
**Currency**: USD  
**Monthly Amount**: 10.00  
**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.