--- title: "Pediatric dentistry: knowledge base using Django" description: "A knowledge base blueprint for pediatric dentistry built with Django on Ample." canonical_url: "https://ample.computer/blueprints/pediatric-dentistry/knowledge-base/django" last_updated: "2026-09-20" --- # Pediatric dentistry: knowledge base using Django Canonical URL: https://ample.computer/blueprints/pediatric-dentistry/knowledge-base/django Formats: [HTML](https://ample.computer/blueprints/pediatric-dentistry/knowledge-base/django) | [Markdown](https://ample.computer/blueprints/pediatric-dentistry/knowledge-base/django.md) | [JSON contract](https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Apediatric-dentistry%3Aknowledge-base%3Adjango) Recipe ID: `page:blueprints:pediatric-dentistry:knowledge-base:django` | Revision: `r1` | Catalog revision: `cat_f13ab9a494120b5e` Status: release `published`, support `verified`, execution `ready` ## Summary A knowledge base blueprint for pediatric dentistry built with Django on Ample. Domain schema: services (code, name, age_range, description): age-appropriate services; first_visit_guides (age_range, checklist, what_parents_bring): public preparation guidance; locations (name, address, phone, opening_hours, child_facilities): practice locations; providers (name, registration_number, pediatric_certification): clinicians; asset_versions (version, cdn_key, published_at): versioned assets served from the CDN bucket. Public information: services by age range, first-visit guidance, locations with child facilities, provider credentials. Kept out of scope until handling is reviewed: minor patient identity and guardians, clinical records, school and consent forms. Data about minors is doubly sensitive; only public practice information belongs in these workflows. 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. Path: [Agent hosting discovery](/discover/discovery) / [Industries and specialties](/discover/industry) / [Dentistry](/discover/industry/dentistry) / [Pediatric dentistry](/discover/industry/pediatric-dentistry) / [Pediatric dentistry: knowledge base using Django](/blueprints/pediatric-dentistry/knowledge-base/django) ## Infrastructure requirements - [Compute](/discover/primitive/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](/discover/primitive/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 pediatric dentistry 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 pediatric dentistry domain.** Create the tables services, first_visit_guides, locations, providers, asset_versions. Age-appropriate services lives in services; keep the sensitive classes (minor patient identity and guardians, clinical records, school and consent forms) out of this schema. 2. **Workflow step 1.** Model articles and categories as tables keyed to the public catalog entities 3. **Workflow step 2.** Build the site with versioned assets served from the CDN bucket 4. **Workflow step 3.** Keep articles free of any sensitive data class 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 --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 pediatric dentistry workflow. ``` ample logs --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) ## Cost estimate Estimated 5.00 USD per month (size prices from pricing.toml at build revision 515b7316fc6e5a81679407ae0c811146ceb2c5c7). - 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 (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 Pediatric dentistry schema and workflow below build on that verified basis and were not separately executed. (expires 2027-03-19T03:31:44Z) Last verified: 2026-09-20T03:31:44Z ## Execution binding MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `876465fce906da0c` observed 2026-09-22T00:31:22.774679+00:00 at revision `e6446ceea69b`, binding state `current`, required scopes: servers:write, buckets:read. ## Input schema ```json { "additionalProperties": false, "properties": { "env": { "description": "Encrypted environment variables", "items": { "pattern": "^[A-Z][A-Z0-9_]*=.*$", "type": "string" }, "maxItems": 50, "type": "array" }, "name": { "description": "App name", "maxLength": 63, "minLength": 1, "pattern": "^[a-z0-9-]+$", "type": "string" }, "path": { "description": "Project directory or ample.toml service", "maxLength": 512, "minLength": 1, "type": "string" }, "release_command": { "description": "Migration command run before activation", "maxLength": 512, "type": "string" }, "start": { "description": "Start command", "maxLength": 512, "type": "string" } }, "required": [ "env", "name", "path", "start" ], "type": "object" } ``` ## Next actions - Browse the catalog index (GET /v1/catalog on the api origin; auth: false, approval: false) - Search published recipes by intent, stack and constraints (POST /v1/catalog/search on the api origin; auth: false, approval: false) - Prepare a side-effect-free deployment plan for an authorized project (POST /v1/catalog/plan on the api origin; auth: true, approval: false) - Read the existing agent authentication setup (GET /mcp/setup on the api origin; auth: false, approval: false) - Browse Pediatric dentistry (GET /v1/catalog/nodes/industry%3Apediatric-dentistry on the api origin; auth: false, approval: false) - Browse Knowledge base (GET /v1/catalog/nodes/workload%3Aknowledge-base on the api origin; auth: false, approval: false) - Browse Django (GET /v1/catalog/nodes/stack%3Aframework-django on the api origin; auth: false, approval: false) - Browse Deploy web app (GET /v1/catalog/nodes/intent%3Adeploy-web-app on the api origin; auth: false, approval: false) Actions describe possible next steps. They are typed data, not commands, and grant no permission.