Law firms: client portal using Django · Ample Computer

Law firms: client portal using Django

A client portal blueprint for law firms built with Django on Ample. Domain schema:

What it runs on

You need

Exact tested configuration

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 law firms domain. Create the tables client_entities, matters, document_requests, shared_documents, document_access. Clients with conflict-check status live in client_entities; keep the sensitive classes (privileged communications and case files, identity and financial documents, opposing-party information) out of this schema.

  2. Workflow step 1. Model client entities and engagement periods; every document belongs to one engagement.

  3. Workflow step 2. Authorize by client entity and role before any storage access (401 without identity, 403 for the wrong client).

  4. Workflow step 3. Store documents in the private bucket and stream them through the app.

  5. Workflow step 4. Deploy and verify the negative authorization 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 law firms 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 Law firms schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover