Home services: inventory manager using Laravel · Ample Computer

Home services: inventory manager using Laravel

An inventory manager blueprint for home services built with Laravel on Ample. Domain schema: services (sku, name, category, price_from, duration_estimate): service catalog as SKUs; parts_stock (sku, delta, reason, moved_at): parts and consumables movements; jobs (job_no, service_area, status, scheduled_for): jobs as orders with status transitions; job_lines (job_no, sku, qty): services and parts on a job; events (seq, record_type, record_id, kind, at): application-owned history written in the same transaction. Public information: service catalog and pricing from, service areas and hours, licensing and insurance summary. Kept out of scope until handling is reviewed: customer addresses and access notes, payment details. Customer addresses and access instructions are personal data; keep them out until handling is reviewed. Technical basis verified on Laravel: 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).

What it runs on

You need

Exact tested configuration

install
composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader

runtime
php

sizes
1vcpu-1gb

start
frankenphp php-server --listen :$PORT --root public

template
php-8.5

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 SKUs and stock movements; derive stock from movements

  3. Workflow step 2. Apply movements transactionally with an optimistic version check on the SKU

  4. Workflow step 3. Record an event per movement for history

  5. Workflow step 4. Deploy and verify history and rejected stale updates

  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=...
    ```

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