Endodontics: company website using Django · Ample Computer

Endodontics: company website using Django

A company website blueprint for endodontics built with Django on Ample. Domain schema: procedures (code, name, description, typical_visits): root canal and retreatment procedures; referral_guides (procedure_id, referring_dentist_checklist, imaging_needed): public guidance for referring practices; locations (name, address, phone, opening_hours): clinic locations; endodontists (name, registration_number, technologies): specialists and equipment listed publicly; asset_versions (version, cdn_key, published_at): versioned assets served from the CDN bucket. Public information: procedure catalog, referral guidance for general dentists, specialist profiles and technology, locations. Kept out of scope until handling is reviewed: referral letters with patient identity, imaging files, clinical notes. Referral documents carry patient identity; keep them out of these workflows until handling is 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

installpython3 -m pip install --target .ample/python -r requirements.txt

runtimepython

sizes-1vcpu-1gb

startPYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py

templatepython-3.12

Steps

  1. Model the endodontics domain. Create the tables procedures, referral_guides, locations, endodontists, asset_versions. Root canal and retreatment procedures live in procedures; keep the sensitive classes (referral letters with patient identity, imaging files, clinical notes) out of this schema.

  2. Workflow step 1. Model the public catalog as tables and render pages from them.

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

  4. Workflow step 3. Keep every sensitive data class out of the site; link to separate, authorized systems instead.

  5. Workflow step 4. Deploy and verify the public URL and the CDN asset URL.

  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 endodontics 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 Endodontics schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover