Host subscription content with Nuxt: relational catalog data · Ample Computer
Host subscription content with Nuxt: relational catalog data
Deploy a subscription content 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). The subscription content-specific behavior (your domain records, validation rules and concurrency policy) is your application code on that verified basis.
Verified November 6, 2026
What it runs on
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgresverified
Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and noDATABASE_URLis supplied.
You need
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_URLat runtime (auto-provisioned when omitted, or supplied with --env)An Ample account token with
servers:write,databases:read
Exact tested configuration
- build:
npm run build --if-present - install:
npm install - runtime:
node - sizes:
1vcpu-1gb - start:
npm run start - template:
node-22
Steps
Build and start.
nuxt buildthennode .output/server/index.mjs(reads HOST and PORT) on the node-22 template. The server must bind 0.0.0.0 on PORT.Implement the pattern on PostgreSQL. The fixture's module implements transactional workflows: 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). Copy the approach into your schema; keep migrations idempotent and run them with--release-command.Deploy. Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 needs an answer first). Re-running with no change is a no-op.
$ ample deploy . --name <app-name> --public
```
4. **Verify.** Fetch the live URL and the pattern self-test route(s) (`/api/p/transactional-workflows`) from the example; then run your own checks. On failure read `ample logs <deployment_id> --kind build` then `--kind runtime`.
$ ample logs <deployment_id> --kind build
```
How it was checked
✓ app responds on its public URL · http get/ → “ample canary nuxt patterns”
✓ transactional-workflows self-test · http get/api/p/transactional-workflows → “tx=ok history=2 conflict=rejected”
Evidence
November 6, 2026 · canary run
Nuxt pattern fixture deployed on Ample (nuxt build then node .output/server/index.mjs (reads HOST and PORT) on the node-22 template); checks passed for transactional-workflows and configuration-secrets. Pattern proof: 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).November 5, 2026 · canary run
The same Nuxt app deployed with a--release-commandmigration; the marker it created was readable after activation.
Tested examples
- Nuxt pattern fixture. Multi-pattern Nuxt app whose transactional workflows module was checked live; the module is under
tests/deploy-canaries/_pattern-modules.
What it doesn’t cover
- Verified on the node-22 template at
s-1vcpu-1gbwith the example fixture. - The pattern checks verified the platform side; the subscription content itself (your domain records, validation rules and concurrency policy) is your application code.
- Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.