Cosmetic dentistry: company website using Laravel · Ample Computer

Cosmetic dentistry: company website using Laravel

A company website blueprint for cosmetic dentistry built with Laravel on Ample. Domain schema:

Public information: treatment catalog with session counts, consented case galleries, financing options, locations and hours. Kept out of scope until handling is reviewed: patient photographs without documented consent, clinical records, payment details. Case photographs are patient data; publish only with documented consent and de-identification. 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

Steps

  1. Model the cosmetic dentistry domain. Create the tables treatments, before_after_galleries, locations, financing_options, asset_versions. Whitening, veneers, bonding and aligner offerings lives in treatments; keep the sensitive classes (patient photographs without documented consent, clinical records, payment details) 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 --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 cosmetic dentistry workflow.
$ 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 Cosmetic dentistry schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover