Logistics operators: reporting dashboard using Django · Ample Computer

Logistics operators: reporting dashboard using Django

A reporting dashboard blueprint for logistics operators built with Django 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; exports (id, definition, object_key, row_count, generated_at, authorized_role): generated artifacts and who may download them. 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 Django: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3).

What it runs on

You need

Exact tested configuration

installpython3 -m pip install --target .ample/python -r requirements.txt
runtimepython
sizes-1vcpu-1gb
startPYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py
templatepython-3.12

Steps

  1. Model the logistics operators domain. Create the tables service_products, capacity_movements, shipments, shipment_lines, exports. 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 report definitions scoped to the agency

  3. Workflow step 2. Generate report artifacts from queries and store them with metadata

  4. Workflow step 3. Authorize downloads (401 without identity)

  5. Workflow step 4. Deploy and verify an authorized export and the rejected anonymous request

  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=...
  1. Verify. Run the pattern self-test(s) from the example (/p/generated-downloads) 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 django patterns”
✓ generated-downloads self-test from the example · http get/p/generated-downloads → “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 generated downloads checks passed: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). The blueprint's Logistics operators schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover