Architecture practices: form collection using Django · Ample Computer

Architecture practices: form collection using Django

A form collection blueprint for architecture practices built with Django on Ample. Domain schema:

Public information: portfolio and services, team and accreditations, studio locations.
Kept out of scope until handling is reviewed: unreleased drawings and site surveys, planning submissions before filing, client contact details.
Drawings and surveys are client-confidential until issued; the portal models per-project authorization only.
Technical basis verified on Django: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok).

What it runs on

You need

Exact tested configuration

Steps

  1. Model the architecture practices domain.
    Create the tables client_entities, projects, drawing_sets, approvals, uploads. Clients and project sites live in client_entities; keep the sensitive classes (unreleased drawings and site surveys, planning submissions before filing, client contact details) out of this schema.

  2. Workflow step 1.
    Model document requests per engagement with due dates and status

  3. Workflow step 2.
    Validate uploaded files (type, size) before storing them in the private bucket and linking them to the request

  4. Workflow step 3.
    Authorize uploads by client entity

  5. Workflow step 4.
    Deploy and verify rejection of disallowed files and a linked upload

  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/browser-file-uploads) and your own acceptance checks for the architecture practices workflow.

    $ ample logs <deployment_id> --kind build
    

How it was checked

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 browser file uploads checks passed: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok).
    The blueprint's Architecture practices schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover