Restaurants: inventory manager using Django · Ample Computer

Restaurants: inventory manager using Django

An inventory manager blueprint for restaurants built with Django 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 Django: 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).

What it runs on

You need

Exact tested configuration

install python3 -m pip install --target .ample/python -r requirements.txt

runtime python

sizes-1vcpu-1gb

start PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py

template python-3.12

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.

    $ ample deploy . --name <app-name> --public --start "python3 run.py" --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
    

How it was checked

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

Evidence

  1. November 6, 2026 · canary run

Django pattern fixture deployed on Ample (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 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.

Tested examples

What it doesn’t cover