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
- Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes. - Postgresverified
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
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 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 logistics operators 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
- 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.
- 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 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
- 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
- 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 logistics operators schema and workflow are an original design for this blueprint, built on that basis.
- Customs and consignee data are sensitive; only shipment status is 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.