Pediatric dentistry: knowledge base using Laravel · Ample Computer

Pediatric dentistry: knowledge base using Laravel

A knowledge base blueprint for pediatric dentistry built with Laravel on Ample. Domain schema:

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. Technical basis verified on Laravel: 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

install
composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader

runtime
php

sizes

start
frankenphp php-server --listen :$PORT --root public

template
php-8.5

Steps

  1. Model the pediatric dentistry domain. Create the tables services, first_visit_guides, locations, providers, asset_versions. Age-appropriate services live 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 <app-name> --public --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.

```sh
    $ ample logs <deployment_id> --kind build
    ```

## How it was checked

✓ app responds on its public URL· http get/ → “ample canary laravel 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  
Laravel pattern fixture deployed on Ample (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 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.

## Tested examples

- **Laravel pattern fixture.** Verified public web service basis for this blueprint.

## What it doesn’t cover

- The technical basis (public web service on Laravel) was verified with the pattern fixture; the pediatric dentistry schema and workflow are an original design for this blueprint, built on that basis.
- Data about minors is doubly sensitive; only public practice information belongs in these workflows.
- Verified on the php-8.5 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-url` returns presigned upload URLs.