Hospitality: public directory using Laravel · Ample Computer
Hospitality: public directory using Laravel
A public directory blueprint for hospitality built with Laravel 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 Laravel: 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
Compute: Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes. Computeverified
Postgres: 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. Postgresverified
CDN: 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. CDNverified
You need
- A Laravel project (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template)
- A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted)
- Bucket credentials from
ample bucket createpassed 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
composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader- runtime: php
- sizes: 1vcpu-1gb
frankenphp php-server --listen :$PORT --root public- template: php-8.5
Steps
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.
Workflow step 1. Model listings with a publishing_status state machine scoped to the agency.
Workflow step 2. Serve only published listings, with media from the CDN bucket.
Workflow step 3. Enforce the agency scope on every query.
Workflow step 4. Deploy and verify a published listing and that unpublished listings are absent.
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=...
- 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 laravel patterns”
✓ relational-records self-test from the example· http get/p/relational-records → “see the pattern fixture checks”
Evidence
- November 6, 2026 · canary run.
Laravel pattern fixture deployed on Ample (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 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
- Laravel pattern fixture. Verified relational records basis for this blueprint.
What it doesn’t cover
- The technical basis (relational records on Laravel) 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 php-8.5 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-urlreturns presigned upload URLs.