Logistics operators: public directory using Laravel · Ample Computer

Logistics operators: public directory using Laravel

A public directory blueprint for logistics operators built with Laravel on Ample. Domain schema:
service_products (sku, name, mode, transit_days, price_basis): shipping services as SKUs;
capacity_movements (sku, lane, date, delta, reason): capacity as stock movements;
shipments (shipment_no, lane, status, booked_at): shipments with status transitions;
shipment_lines (shipment_no, sku, units): shipment contents;
state_transitions (record_type, from_state, to_state): the allowed state machine. Public information: service products and transit times, lanes served, tracking entry point.
Kept out of scope until handling is reviewed: consignee addresses, commercial invoices, customs documents. Customs and consignee data are sensitive; only shipment status is 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

You need

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 logistics operators domain. Create the tables service_products, capacity_movements, shipments, shipment_lines, state_transitions. Shipping services as skus lives in service_products; keep the sensitive classes (consignee addresses, commercial invoices, customs documents) 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 logistics operators 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

  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 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 Logistics operators schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover