Equipment rental: inventory manager using Laravel · Ample Computer
Equipment rental: inventory manager using Laravel
An inventory manager 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).
What it runs on
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgresverified
Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.S3-compatible object storageverified
Buckets speak the S3 API with SigV4 credentials Ample Computer issues;ample bucket upload-urlreturns a presigned upload URL. PutObject and GetObject are checked by canary.
You need
- 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
Exact tested configuration
installcomposer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader- runtimephp
- sizes-1vcpu-1gb
startfrankenphp php-server --listen :$PORT --root public- templatephp-8.5
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 SKUs and stock movements; derive stock from movements
Workflow step 2. Apply movements transactionally with an optimistic version check on the SKU
Workflow step 3. Record an event per movement for history
Workflow step 4. Deploy and verify history and rejected stale updates
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=...Verify. Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the equipment rental 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
- 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 Equipment rental schema and workflow below build on that verified basis.
Tested examples
- Laravel pattern fixture. Verified transactional workflows basis for this blueprint.
What it doesn’t cover
- 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, built on that basis.
- Identity verification and deposits are outside these flows; only availability and rental status are modeled.
- Verified on the php-8.5 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector.
- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture);
ample bucket upload-urlreturns presigned upload URLs.