Endodontics: campaign site using Django

Summary

A campaign site 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. No compliance is claimed. 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.

Infrastructure requirements

• Compute: verified (Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.)
• CDN: verified (The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.)

Prerequisites

• 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)
• Bucket credentials from ample bucket create passed as encrypted S3_* environment variables and a published bucket for public assets (CDN_*)
• A review of which endodontics data classes may be handled at all; this blueprint models public information only

Exact tested configuration

• template: python-3.12
• runtime: python
• size: s-1vcpu-1gb
• install: python3 -m pip install --target .ample/python -r requirements.txt
• start: PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py

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 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=...
   

7. 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
   

Tested examples

• Django pattern fixture (tests/deploy-canaries/django-patterns): Verified public web service basis for this blueprint.

Success checks

• App responds on its public URL (/ on the live URL, expect ample canary django patterns)
• Versioned-static-assets self-test from the example (/p/versioned-static-assets on the live URL, expect see the pattern fixture checks)

Limitations

• The technical basis (public web service on Django) was verified with the pattern fixture; the endodontics schema and workflow are an original design for this blueprint and were not executed as a separate application.
• No health, financial, privacy or other compliance claim is made. Referral documents carry patient identity; keep them out of these workflows until handling is reviewed. No compliance is claimed.
• Public content and synthetic examples only until actual data-handling requirements have been reviewed.
• Verified on the python-3.12 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.
• PutObject and GetObject with path-style addressing are verified; other S3 operations and CDN cache rules are not.

Cost estimate

Estimated 5.00 USD per month (size prices from pricing.toml at build revision a1b8c38919e59cd035ebabaced73cf84ece24371).

• App server x1 s-1vcpu-1gb: 5.00 USD

Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

Verification evidence

• canary_run on 2026-09-20T03:31:44Z at revision 03b6402b1b3e19178985f08ea4033804521d85d4-dirty (CLI b75e104): 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 and were not separately executed. (expires 2027-03-19T03:31:44Z)