page:blueprints:equipment rental:product catalog:laravel

Equipment rental: product catalog using Laravel

Industry blueprint

A product catalog blueprint for equipment rental built with Laravel on Ample. Domain schema:

Public information: equipment catalog and rates, availability calendar, deposit and insurance terms. Kept out of scope until handling is reviewed: renter identity documents, payment and deposit details. Identity verification and deposits are outside these flows; only availability and rental status are modeled.

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

Representative Queries

Resource Requirements

Infrastructure Requirements

Prerequisites

  1. 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)
  2. A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted)
  3. Bucket credentials from ample bucket create passed as encrypted S3_* environment variables
  4. A review of which equipment rental data classes may be handled at all; this blueprint models public information only

Tested Configuration

Workflow Steps

  1. Model the equipment rental domain: Create the tables equipment, stock_movements, rentals, rental_lines, events. Rental catalog lives in equipment; keep the sensitive classes (renter identity documents, payment and deposit details) out of this schema.
  2. Workflow step 1: Model the SKU catalog with versioned updates
  3. Workflow step 2: Record every catalog change as an event in the same transaction
  4. Workflow step 3: Reject stale concurrent updates
  5. Workflow step 4: Deploy and verify history and conflict handling
  6. Deploy: Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
    • Command: ample deploy . --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 equipment rental workflow.
    • Command: ample logs --kind build

Examples

Success Checks

Limitations

Cost Estimate

Evidence Summary

Last Verified At

2026-09-20T20:36:21Z

Formats

Next Actions

  1. Browse the catalog index - GET /v1/catalog
  2. Search published recipes by intent - POST /v1/catalog/search
  3. Prepare a side-effect-free deployment plan - POST /v1/catalog/plan
  4. Read the existing agent authentication setup - GET /mcp/setup
  5. Browse Equipment rental - GET /v1/catalog/nodes/industry%3Aequipment-rental
  6. Browse Product catalog - GET /v1/catalog/nodes/workload%3Aproduct-catalog
  7. Browse Laravel - GET /v1/catalog/nodes/stack%3Aframework-laravel
  8. Browse Deploy web app - GET /v1/catalog/nodes/intent%3Adeploy-web-app