# Property management: reporting dashboard using Django

A reporting dashboard 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; 
- **exports** (id, definition, object_key, row_count, generated_at, authorized_role): generated artifacts and who may download them. 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: 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

- [Computeverified](/content/discover/primitive/compute/index.html)  
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgresverified](/content/discover/primitive/postgres/index.html)  
Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

- [S3-compatible object storageverified](/content/discover/primitive/s3-compatible-object-storage/index.html)  
Buckets speak the S3 API with SigV4 credentials Ample Computer issues; `ample bucket upload-url` returns a presigned upload URL. PutObject and GetObject are checked by canary.

## You need

- A Django project (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 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 property management data classes may be handled at all; this blueprint models public information only

## Exact tested configuration

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

## Steps

1. **Model the property management domain.** Create the tables listings, agencies, maintenance_vendors, reports, exports. 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 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=...
   ```
7. **Verify.** Run the pattern self-test(s) from the example (/p/generated-downloads) 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”  
✓ 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 Property management schema and workflow below build on that verified basis.

## Tested examples

- **Django pattern fixture.** Verified generated downloads basis for this blueprint.

## What it doesn’t cover

- The technical basis (generated downloads on Django) was verified with the pattern fixture; the property management schema and workflow are an original design for this blueprint, built on that basis.
- Tenant data is personal and often regulated; only published listings and office-scoped reporting are modeled.
- Verified on the python-3.12 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector.
- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture); `ample bucket upload-url` returns presigned upload URLs.
