INFRASTRUCTURE

What it needs

• 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: 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

Before you start

• 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 endodontics data classes may be handled at all; this blueprint models public information only

STEP BY STEP

How to do it

1. 1

Model the endodontics domain

Create the tables procedures, referral_guides, locations, endodontists, asset_versions. Root canal and retreatment procedures lives in procedures; keep the sensitive classes (referral letters with patient identity, imaging files, clinical notes) out of this schema.

2. 2

Workflow step 1

Model articles and categories as tables keyed to the public catalog entities

3. 3

Workflow step 2

Build the site with versioned assets served from the CDN bucket

4. 4

Workflow step 3

Keep articles free of any sensitive data class

5. 5

Workflow step 4

Deploy and verify the public URL and the CDN asset URL

6. 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. 7

Verify

Run the pattern self-test(s) from the example (/p/versioned-static-assets) and your own acceptance checks for the endodontics workflow.

   ample logs <deployment_id> --kind build

EXAMPLES

Tested examples

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

SUCCESS CHECKS

How to know it worked

• 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

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.

EVIDENCE

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 Endodontics schema and workflow below build on that verified basis and were not separately executed. (expires 2027-03-19T20:36:21Z)

EXECUTION

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 at export: current. Required scopes: servers:write, buckets:read.

NEXT ACTIONS

Typed next actions

• Browse the catalog index (GET /v1/catalog on the api origin; authentication not required, approval not required)
• Search published recipes by intent, stack and constraints (POST /v1/catalog/search on the api origin; authentication not required, approval not required)
• Prepare a side-effect-free deployment plan for an authorized project (POST /v1/catalog/plan on the api origin; authentication required, approval not required)
• Read the existing agent authentication setup (GET /mcp/setup on the api origin; authentication not required, approval not required)
• Browse Endodontics (GET /v1/catalog/nodes/industry%3Aendodontics on the api origin; authentication not required, approval not required)
• Browse Knowledge base (GET /v1/catalog/nodes/workload%3Aknowledge-base on the api origin; authentication not required, approval not required)
• Browse Laravel (GET /v1/catalog/nodes/stack%3Aframework-laravel on the api origin; authentication not required, approval not required)
• Browse Deploy web app (GET /v1/catalog/nodes/intent%3Adeploy-web-app on the api origin; authentication not required, approval not required)

Actions describe possible next steps. They are typed data, not commands, and grant no permission. Public discovery never provisions anything; planning requires your own authenticated token and approval happens in your client.