# Hospitality: vendor portal using Laravel

A vendor portal 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;  
- **document_access** (`document_id`, `principal_reference`, `role`, `granted_at`): who may read which document.

Public information: room types, amenities and rates, 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 role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok).

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

- **[S3-compatible object storageverified](/content/discover/primitive/s3-compatible-object-storage/index.html)**  
Buckets speak the S3 API with SigV4 credentials Ample Computer issues; `ample bucket upload-url` returns a presigned upload URL. PutObject and GetObject are checked by canary.

## 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 create` passed as encrypted S3_* environment variables
- A review of which hospitality data classes may be handled at all; this blueprint models public information only

## Exact tested configuration

install  
`composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader`

runtime  
`php`

sizes  
`1vcpu-1gb`

start  
`frankenphp php-server --listen :$PORT --root public`

template  
`php-8.5`

## Steps

1. **Model the hospitality domain.** Create the tables room_types, inventory_movements, bookings, booking_lines, document_access. 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 vendors scoped to the agency with roles

3. **Workflow step 2.** Authorize document access by vendor and role (401, 403 negative tests)

4. **Workflow step 3.** Store vendor documents in the private bucket

5. **Workflow step 4.** Deploy and verify the negative tests and an authorized download

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

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

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

```sh
$ ample logs <deployment_id> --kind build
```

## How it was checked

✓ app responds on its public URL · http get/ → “ample canary laravel patterns”  
✓ private-document-library self-test from the example · http get/p/private-document-library → “see the pattern fixture checks”

## Evidence

1. 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 private document library checks passed: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). The blueprint's Hospitality schema and workflow below build on that verified basis.

## Tested examples

- **Laravel pattern fixture.** Verified private document library basis for this blueprint.

## What it doesn’t cover

- The technical basis (private document library 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-url` returns presigned upload URLs.
