Equipment rental: product catalog using Next.js · Ample Computer

Equipment rental: product catalog using Next.js

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

What it runs on

You need

Exact tested configuration

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.

   $ 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 equipment rental workflow.
   $ ample logs <deployment_id> --kind build

How it was checked

✓ app responds on its public URL · http get/ → “ample canary next js patterns”
✓ transactional-workflows self-test from the example · http get/p/transactional-workflows → “see the pattern fixture checks”

Evidence

  1. November 5, 2026 · canary run

Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 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

What it doesn’t cover