page:recipes:blog:nuxt:relational content

Host blog with Nuxt: Postgres-backed content

Deploy a blog built with Nuxt on Ample using the relational records 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, and a published bucket serves public assets from the CDN host. Verified on Nuxt: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Not separately tested: your record schema, states and access rules; treat the blog-specific behavior as your application code.

Representative Queries

Resource Requirements

Infrastructure Requirements

  1. Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
  2. 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.
  3. CDN: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

Prerequisites

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 relational records: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions...
  3. Wire object storage: Create the bucket(s), then pass endpoint, region, bucket and keys as --env values.
  4. Deploy: Run the synchronous deploy once and read the result...
  5. Verify: Fetch the live URL and the pattern self-test route(s)...

Examples

Success Checks

  1. app responds on its public URL
  2. relational-records self-test

Limitations

Cost Estimate

Last Verified At

Unknowns

Formats