General dentistry: campaign site using Laravel · Ample Computer
General dentistry: campaign site using Laravel
A campaign site blueprint for general dentistry built with Laravel 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 information includes a service catalog with prices, locations, hours, and parking, clinician profiles and registrations, accepted insurance plans.
Patient data is health data. Keep it out of these workflows until handling requirements have been reviewed.
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
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 Laravel project (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)
- 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
installcomposer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader- runtimephp
- sizes-1vcpu-1gb
- startfrankenphp php-server --listen :$PORT --root public
- templatephp-8.5
Steps
Model the general dentistry domain. Create the tables services, locations, dentists, insurance_plans, asset_versions. The treatments a practice offers lives in services.
Workflow step 1. Model the campaign's offers and locations as tables with start and end dates.
Workflow step 2. Build the site and publish versioned static assets to the CDN bucket.
Workflow step 3. Collect no personal data on the site itself; hand off to an authorized system.
Workflow step 4. Deploy, verify the public URL and the CDN asset URL, and retire the campaign by the end date.
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=...
- 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 laravel 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: 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 General dentistry schema and workflow 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 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 have been reviewed.
- 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-urlreturns presigned upload URLs.