# Hospitality: public directory using Next.js

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

- **room_types** (sku, name, capacity, base_rate, amenities): room and package catalog;  
- **inventory_movements** (sku, date, delta, reason): availability per date as stock movements;  
- **bookings** (booking_no, check_in, check_out, status): bookings with status transitions;  
- **booking_lines** (booking_no, sku, nights, rate): booking contents;  
- **state_transitions** (record_type, from_state, to_state): the allowed state machine.

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

- [Computeverified](/content/discover/primitive/compute/index.html)  
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgresverified](/content/discover/primitive/postgres/index.html)  
Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

- [CDNverified](/content/discover/primitive/cdn/index.html)  
A published bucket's objects are served from its public URL; set Cache-Control when uploading to control caching. App responses are served by the app.

## You need

- A Next.js project (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template)
- A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted)
- Bucket credentials from `ample bucket create` passed as encrypted S3_* environment variables and a published bucket for public assets (CDN_*)
- A review of which hospitality data classes may be handled at all; this blueprint models public information only

## Exact tested configuration

- build  
npm run build --if-present
- install  
npm install
- runtime  
nod
- sizes  
1vcpu-1gb
- start  
npm run start
- template  
node-22

## 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.

```shell
$ 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=...
```

7. **Verify.** Run the pattern self-test(s) from the example (/p/relational-records) and your own acceptance checks for the hospitality workflow.

```shell
$ 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

- **Next.js pattern fixture.** Verified relational records basis for this blueprint.

## What it doesn’t cover

- The technical basis (relational records on Next.js) was verified with the pattern fixture; the hospitality schema and workflow are an original design for this blueprint, built on that basis.
- Guest identity documents are sensitive; only availability and booking status are modeled here.
- Verified on the node-22 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector.
- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture); `ample bucket upload-url` returns presigned upload URLs.
