# Property management: public directory using Django

A public directory 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;
- **state_transitions** (record_type, from_state, to_state): the allowed state machine.

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 workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true).

Verified November 6, 2026

## 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.
- [CDNverified](/content/discover/primitive/cdn/index.html)  
  A published bucket's objects are served from its public URL; set Cache-Control when uploading to control caching. App responses are served by the app.

## 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 and a published bucket for public assets (CDN_*)
- A review of which property management data classes may be handled at all; this blueprint models public information only

## 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 property management domain.**  
   Create the tables listings, agencies, maintenance_vendors, reports, state_transitions. Rental listings with publishing status live 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 listings with a publishing_status state machine scoped to the agency

3. **Workflow step 2.**  
   Serve only published listings, with media from the CDN bucket

4. **Workflow step 3.**  
   Enforce the agency scope on every query

5. **Workflow step 4.**  
   Deploy and verify a published listing and that unpublished listings are absent

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=... --env CDN_PUBLIC_URL=...
```

7. **Verify.**  
   Run the pattern self-test(s) from the example (/p/relational-records) 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”  
✓ relational-records self-test from the example · http get/p/relational-records → “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 relational records checks passed: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). The blueprint's Property management schema and workflow below build on that verified basis.

## Tested examples

- **Django pattern fixture.** Verified relational records basis for this blueprint.

## What it doesn’t cover

- The technical basis (relational records 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.
