General dentistry: campaign site using Django · Ample Computer

General dentistry: campaign site using Django

A campaign site blueprint for general dentistry built with Django on Ample. Domain schema:

Public information: service catalog with prices from, locations, hours and parking, clinician profiles and registrations, accepted insurance plans. Kept out of scope until handling is reviewed: patient identity and contact details, clinical records, x-rays and treatment notes, appointment history tied to a person. Patient data is health data. Keep it out of these workflows until handling requirements (for example HIPAA in the United States) have been reviewed. Technical basis verified on Django: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL.

What it runs on

You need

Exact tested configuration

Steps

  1. Model the general dentistry domain. Create the tables services, locations, dentists, insurance_plans, asset_versions. The treatments a practice offers lives in services; keep the sensitive classes (patient identity and contact details, clinical records, x-rays and treatment notes, appointment history tied to a person) out of this schema.

  2. Workflow step 1. Model the campaign's offers and locations as tables with start and end dates

  3. Workflow step 2. Build the site and publish versioned static assets to the CDN bucket

  4. Workflow step 3. Collect no personal data on the site itself; hand off to an authorized system

  5. Workflow step 4. Deploy, verify the public URL and the CDN asset URL, and retire the campaign by end date

  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=...
  1. Verify. Run the pattern self-test(s) from the example (/p/versioned-static-assets) and your own acceptance checks for the general dentistry workflow.
$ ample logs <deployment_id> --kind build

How it was checked

✓ App responds on its public URL · http get/ → “ample canary django patterns”
✓ Versioned-static-assets self-test from the example · http get/p/versioned-static-assets → “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 public web service checks passed: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL. The blueprint's General dentistry schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover