Home services: order tracking using Laravel · Ample Computer

Home services: order tracking using Laravel

An order tracking blueprint for home services built with Laravel on Ample. Domain schema:

What it runs on

You need

Exact tested configuration

Steps

  1. Model the home services domain. Create the tables services, parts_stock, jobs, job_lines, events. Service catalog as skus lives in services; keep the sensitive classes (customer addresses and access notes, payment details) out of this schema.
  2. Workflow step 1. Model orders with explicit status transitions and order lines
  3. Workflow step 2. Apply status changes transactionally and record an event per change
  4. Workflow step 3. Expose status history to authorized callers only
  5. Workflow step 4. Deploy and verify history and conflict rejection
  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=...
  1. Verify. Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the home services workflow.
   $ ample logs <deployment_id> --kind build

How it was checked

✓ app responds on its public URL · http get/ → “ample canary laravel patterns”
✓ transactional-workflows self-test from the example · http get/p/transactional-workflows → “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 transactional workflows checks passed: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). The blueprint's Home services schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover