Construction contractors: vendor portal using Django · Ample Computer

Construction contractors: vendor portal using Django

A vendor portal blueprint for construction contractors built with Django on Ample. Domain schema:

Public information: published project showcases, services and regions, licenses and insurance summary. Kept out of scope until handling is reviewed: site safety incidents, bid pricing, client contracts. Safety and bid data are confidential; only published showcases and branch reporting are modeled. Technical basis verified on Django: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok).

What it runs on

You need

Exact tested configuration

Steps

  1. Model the construction contractors domain. Create the tables listings, agencies, vendors, reports, document_access. Showcase projects with publishing status lives in listings; keep the sensitive classes (site safety incidents, bid pricing, client contracts) out of this schema.
  2. Workflow step 1. Model vendors scoped to the agency with roles
  3. Workflow step 2. Authorize document access by vendor and role (401, 403 negative tests)
  4. Workflow step 3. Store vendor documents in the private bucket
  5. Workflow step 4. Deploy and verify the negative tests and an authorized download
  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/private-document-library) and your own acceptance checks for the construction contractors workflow.
    $ ample logs <deployment_id> --kind build
    

How it was checked

✓ app responds on its public URL · http get/ → “ample canary django patterns”

✓ private-document-library self-test from the example · http get/p/private-document-library → “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 private document library checks passed: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). The blueprint's Construction contractors schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover