General dentistry: company website using Django · Ample Computer
General dentistry: company website using Django
A company website blueprint for general dentistry built with Django on Ample. Domain schema:
- services (code, name, description, duration_minutes, price_from): the treatments a practice offers;
- locations (name, address, phone, opening_hours, accessibility_notes): each practice location;
- dentists (name, registration_number, specialties, location_id): the clinicians listed publicly;
- insurance_plans (name, accepted_at_location_id): plans accepted per location;
- asset_versions (version, cdn_key, published_at): versioned assets served from the CDN bucket.
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
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.CDNverified
A published bucket's objects are served from its public URL; set Cache-Control when uploading to control caching. App responses are served by the app.
You need
- 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 createpassed as encrypted S3_* environment variables and a published bucket for public assets (CDN_*) - A review of which general dentistry data classes may be handled at all; this blueprint models public information only
Exact tested configuration
install python3 -m pip install --target .ample/python -r requirements.txtruntime pythonsizes-1vcpu-1gbstart PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.pytemplate python-3.12
Steps
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.
Workflow step 1. Model the public catalog as tables and render pages from them.
Workflow step 2. Build the site and publish versioned static assets to the CDN bucket.
Workflow step 3. Keep every sensitive data class out of the site; link to separate, authorized systems instead.
Workflow step 4. Deploy and verify the public URL and the CDN asset URL.
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=...
- 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
- 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
- Django pattern fixture. Verified public web service basis for this blueprint.
What it doesn’t cover
- The technical basis (public web service on Django) was verified with the pattern fixture; the general dentistry schema and workflow are an original design for this blueprint, built on that basis.
- Patient data is health data. Keep it out of these workflows until handling requirements (for example HIPAA in the United States) have been reviewed.
- Verified on the python-3.12 template at s-1vcpu-1gb.
- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture);
ample bucket upload-urlreturns presigned upload URLs.