Property management: vendor portal using Django · Ample Computer

Property management: vendor portal using Django

A vendor portal blueprint for property management built with Django on Ample. Domain schema: listings (reference, address, unit, rent, publishing_status, agency_id): rental listings with publishing status; agencies (name, license_number, portfolio_size): management offices; maintenance_vendors (name, trade, agency_id, status): vendors per office; reports (agency_id, period, object_key, generated_at): portfolio reports per office; document_access (document_id, principal_reference, role, granted_at): who may read which document. Public information: available rentals, office contacts, application process. Kept out of scope until handling is reviewed: tenant identity and payment history, inspection reports with personal data. Tenant data is personal and often regulated; only published listings and office-scoped 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

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 property management domain. Create the tables listings, agencies, maintenance_vendors, reports, document_access. Rental listings with publishing status lives in listings; keep the sensitive classes (tenant identity and payment history, inspection reports with personal data) 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=...
  1. Verify. Run the pattern self-test(s) from the example (/p/private-document-library) and your own acceptance checks for the property management 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 Property management schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover