Restaurants: Inventory Manager Using Laravel

Summary

A inventory manager 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 includes: 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.

Infrastructure Requirements

1. Compute

   • Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
   • Status: verified

2. Postgres

   • Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
   • Status: verified

3. S3-compatible Object Storage

   • Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.
   • Status: 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

Workflow 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 SKUs and stock movements; derive stock from movements.

3. Workflow step 2
   Apply movements transactionally with an optimistic version check on the SKU.

4. Workflow step 3
   Record an event per movement for history.

5. Workflow step 4
   Deploy and verify history and rejected stale updates.

6. Deploy
   Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
   Command: ample deploy . --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.
   Command: ample logs --kind build

Success Checks

1. App responds on its public URL: Expected response: ample canary laravel patterns
2. Transactional-workflows self-test from the example: Expected response: 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.
• Verified on the php-8.5 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.

Cost Estimate

• Monthly Amount: 10.0 USD
• Components:
  • App server (s-1vcpu-1gb): $5.0/month
  • Managed PostgreSQL database (s-1vcpu-1gb): $5.0/month

Templates and Definitions

• Tested Configuration:
  • Template: php-8.5
  • Runtime: php
  • Size: s-1vcpu-1gb
  • Install command: composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader
  • Start command: frankenphp php-server --listen :$PORT --root public

Examples

• Laravel Pattern Fixture
  Verified transactional workflows basis for this blueprint.
  Source: tests/deploy-canaries/laravel-patterns