Restaurants: order tracking using Laravel

Summary

A order tracking blueprint for restaurants built with Laravel on Ample. Domain schema: menu_items (sku, name, section, price, allergens, active): the menu as a SKU catalog; stock_movements (sku, delta, reason, moved_at): ingredient and prepared-item stock; orders (order_no, service_type, status, placed_at): dine-in, pickup and delivery orders; order_lines (order_no, sku, qty, modifiers): order contents; events (seq, record_type, record_id, kind, at): application-owned history written in the same transaction. Public information: menu with allergens and prices, locations, hours and reservations contact, catering information. Kept out of scope until handling is reviewed: customer contact and payment details, staff schedules. Allergen information must be kept accurate by the operator; nothing here validates food-safety claims. Technical basis verified on Laravel: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected).

Infrastructure requirements

• Compute: verified (Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.)
• Postgres: verified (Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.)
• S3-compatible object storage: verified (Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.)

Prerequisites

• 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 restaurants data classes may be handled at all; this blueprint models public information only

Exact tested configuration

• template: php-8.5
• runtime: php
• size: s-1vcpu-1gb
• install: composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader
• start: frankenphp php-server --listen :$PORT --root public

Steps

1. Model the restaurants domain. Create the tables menu_items, stock_movements, orders, order_lines, events. The menu as a sku catalog lives in menu_items; keep the sensitive classes (customer contact and payment details, staff schedules) out of this schema.

2. Workflow step 1. Model orders with explicit status transitions and order lines

3. Workflow step 2. Apply status changes transactionally and record an event per change

4. Workflow step 3. Expose status history to authorized callers only

5. Workflow step 4. Deploy and verify history and conflict rejection

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

7. Verify. Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the restaurants workflow.

   ample logs <deployment_id> --kind build
   

Tested examples

• Laravel pattern fixture (tests/deploy-canaries/laravel-patterns): Verified transactional workflows basis for this blueprint.

Success checks

• app responds on its public URL (/ on the live URL, expect ample canary laravel patterns)
• transactional-workflows self-test from the example (/p/transactional-workflows on the live URL, expect see the pattern fixture checks)

Limitations

• The technical basis (transactional workflows on Laravel) was verified with the pattern fixture; the restaurants schema and workflow are an original design for this blueprint and were not executed as a separate application.
• No health, financial, privacy or other compliance claim is made. Allergen information must be kept accurate by the operator; nothing here validates food-safety claims.
• Public content and synthetic examples only until actual data-handling requirements have been reviewed.
• Verified on the php-8.5 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.
• PutObject and GetObject with path-style addressing are verified; other S3 operations and CDN cache rules are not.

Cost estimate

Estimated 10.00 USD per month (size prices from pricing.toml at build revision a1b8c38919e59cd035ebabaced73cf84ece24371).

• app server x1 s-1vcpu-1gb: 5.00 USD
• managed PostgreSQL database x1 s-1vcpu-1gb: 5.00 USD

Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

Verification evidence

• canary_run on 2026-09-20T20:36:21Z at revision 118ad1c6d7d23d4c2ce069254bab9ec9d37cd57b-dirty (CLI 118ad1c): 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 transactional workflows checks passed: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). The blueprint's Restaurants schema and workflow below build on that verified basis and were not separately executed. (expires 2027-03-19T20:36:21Z)

Execution binding

MCP tool ample_deploy (registry mcp:ample_deploy), schema hash 876465fce906da0c observed 2026-09-21T03:19:59.461917+00:00 at revision 49962bcade4f, binding state current, required scopes: servers:write, databases:read, buckets:read.