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:
- equipment (sku, name, category, day_rate, serial_tracked): rental catalog;
- stock_movements (sku, unit_serial, delta, reason, moved_at): check-outs, returns and maintenance;
- rentals (rental_no, period_start, period_end, status): rentals with status transitions;
- rental_lines (rental_no, sku, unit_serial, rate): rental contents;
- events (seq, record_type, record_id, kind, at): application-owned history written in the same transaction.
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
- Equipment rental: product catalog using Laravel
- Where can I host Equipment rental: Product catalog built with Laravel?
- I need a genuinely specialized product catalog workflow covering asset serial numbers, availability windows and return status.
Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage
Infrastructure Requirements
- Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- Postgres: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
- S3-compatible object storage: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.
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)
- A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted)
- Bucket credentials from
ample bucket createpassed as encrypted S3_* environment variables - A review of which equipment rental data classes may be handled at all; this blueprint models public information only
Tested Configuration
- Template: php-8.5
- Runtime: php
- Size: s-1vcpu-1gb
- Install Command: composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader
- Start Command: frankenphp php-server --listen :$PORT --root public
Workflow Steps
- 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.
- Workflow step 1: Model the SKU catalog with versioned updates
- Workflow step 2: Record every catalog change as an event in the same transaction
- Workflow step 3: Reject stale concurrent updates
- Workflow step 4: Deploy and verify history and conflict handling
- 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=...
- 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
- Title: Laravel pattern fixture Description: Verified transactional workflows basis for this blueprint. Source Reference: tests/deploy-canaries/laravel-patterns
Success Checks
- App responds on its public URL (expect: ample canary laravel patterns)
- Transactional-workflows self-test from the example
Limitations
- The technical basis (transactional workflows on Laravel) was verified with the pattern fixture; the equipment rental schema and workflow are an original design for this blueprint and were not executed as a separate application.
- No health, financial, privacy or other compliance claim is made. Identity verification and deposits are outside these flows; only availability and rental status are modeled.
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.
Cost Estimate
- Monthly Amount: 10.0 USD
- Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
- Components:
- app server s-1vcpu-1gb: 5.0 USD
- managed PostgreSQL database s-1vcpu-1gb: 5.0 USD
- Note: 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 Summary
- Kind: canary_run Summary: Laravel pattern fixture deployed on Ample; the transactional workflows checks passed. Observed At: 2026-09-20T20:36:21Z Implementation Revision: 118ad1c6d7d23d4c2ce069254bab9ec9d37cd57b-dirty (CLI 118ad1c)
Last Verified At
2026-09-20T20:36:21Z
Formats
Next Actions
- Browse the catalog index - GET /v1/catalog
- Search published recipes by intent - POST /v1/catalog/search
- Prepare a side-effect-free deployment plan - POST /v1/catalog/plan
- Read the existing agent authentication setup - GET /mcp/setup
- Browse Equipment rental - GET /v1/catalog/nodes/industry%3Aequipment-rental
- Browse Product catalog - GET /v1/catalog/nodes/workload%3Aproduct-catalog
- Browse Laravel - GET /v1/catalog/nodes/stack%3Aframework-laravel
- Browse Deploy web app - GET /v1/catalog/nodes/intent%3Adeploy-web-app