---
title: "General dentistry: campaign site using Laravel"
description: "A campaign site blueprint for general dentistry built with Laravel on Ample."
canonical_url: "https://ample.computer/blueprints/general-dentistry/campaign-site/laravel"
last_updated: "2026-09-20"
---

# General dentistry: campaign site using Laravel

Canonical URL: https://ample.computer/blueprints/general-dentistry/campaign-site/laravel
Formats: [HTML](https://ample.computer/blueprints/general-dentistry/campaign-site/laravel) | [Markdown](https://ample.computer/blueprints/general-dentistry/campaign-site/laravel.md) | [JSON contract](https://api.ample.computer/v1/catalog/recipes/page%3Ablueprints%3Ageneral-dentistry%3Acampaign-site%3Alaravel)
Recipe ID: `page:blueprints:general-dentistry:campaign-site:laravel` | Revision: `r1` | Catalog revision: `cat_f13ab9a494120b5e`

Status: release `published`, support `verified`, execution `ready`

## Summary

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: 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; nothing here establishes compliance. 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.

Path: [Agent hosting discovery](/discover/discovery) / [Industries and specialties](/discover/industry) / [Dentistry](/discover/industry/dentistry) / [General dentistry](/discover/industry/general-dentistry) / [General dentistry: campaign site using Laravel](/blueprints/general-dentistry/campaign-site/laravel)

## 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 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 create` passed 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

- template: `php-8.5`
- runtime: `php`
- size: `s-1vcpu-1gb`
- install: `composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader`
- start: `frankenphp php-server --listen :$PORT --root public`

## Steps

1. **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.
2. **Workflow step 1.** Model the campaign's offers and locations as tables with start and end dates
3. **Workflow step 2.** Build the site and publish versioned static assets to the CDN bucket
4. **Workflow step 3.** Collect no personal data on the site itself; hand off to an authorized system
5. **Workflow step 4.** Deploy, verify the public URL and the CDN asset URL, and retire the campaign by end date
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 general dentistry workflow.

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

## Tested examples

- **Laravel pattern fixture** (tests/deploy-canaries/laravel-patterns): Verified public web service basis for this blueprint.

## Success checks

- app responds on its public URL (`/` on the live URL, expect ample canary laravel 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-20T20:36:21Z at revision `118ad1c6d7d23d4c2ce069254bab9ec9d37cd57b (CLI 118ad1c)`: 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 below build on that verified basis and were not separately executed. (expires 2027-03-19T20:36:21Z)

Last verified: 2026-09-20T20:36:21Z


## 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"
    }
  },
  "required": [
    "env",
    "name",
    "path"
  ],
  "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 General dentistry (GET /v1/catalog/nodes/industry%3Ageneral-dentistry on the api origin; auth: false, approval: false)
- Browse Campaign site (GET /v1/catalog/nodes/workload%3Acampaign-site on the api origin; auth: false, approval: false)
- Browse Laravel (GET /v1/catalog/nodes/stack%3Aframework-laravel 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.