Hospitality: public directory using Next.js · Ample Computer

Hospitality: public directory using Next.js

A public directory blueprint for hospitality built with Next.js on Ample. Domain schema:

Public information: room types, amenities and rates from property location and policies, events and dining. Kept out of scope until handling is reviewed: guest identity documents, payment details, stay history. Guest identity documents are sensitive; only availability and booking status are modeled here. Technical basis verified on Next.js: 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).

What it runs on

You need

Exact tested configuration

Steps

  1. Model the hospitality domain. Create the tables room_types, inventory_movements, bookings, booking_lines, state_transitions. Room and package catalog lives in room_types; keep the sensitive classes (guest identity documents, payment details, stay history) out of this schema.

  2. Workflow step 1. Model listings with a publishing_status state machine scoped to the agency

  3. Workflow step 2. Serve only published listings, with media from the CDN bucket

  4. Workflow step 3. Enforce the agency scope on every query

  5. Workflow step 4. Deploy and verify a published listing and that unpublished listings are absent

  6. Deploy. Run the synchronous deploy once and read the result. Re-running with no change is a no-op.

$ ample deploy . --name <app-name> --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=...
  1. Verify. Run the pattern self-test(s) from the example (/p/relational-records) and your own acceptance checks for the hospitality workflow.
$ ample logs <deployment_id> --kind build

How it was checked

✓ app responds on its public URL· http get/ → “ample canary next js patterns”
✓ relational-records self-test from the example· http get/p/relational-records → “see the pattern fixture checks”

Evidence

  1. November 5, 2026 · canary run

Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template); the relational records checks passed: 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). The blueprint's Hospitality schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover