page:blueprints:home services:order tracking:laravel

Home services: order tracking using Laravel

Summary

A order tracking 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 includes service catalog and pricing, service areas and hours, licensing and insurance summary. Customer addresses and access notes are personal data and are kept out of scope until handling is reviewed.

Technical Overview

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

• Home services: order tracking using Laravel
• Where can I host Home services: Order tracking built with Laravel?
• I need a genuinely specialized order tracking workflow covering service areas, job materials, and field-job status.

Resource Requirements

• Primitive Compute
• Primitive Postgres
• Primitive S3-compatible object storage

Infrastructure Requirements

1. Compute
   • Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
2. 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.
3. S3-compatible object storage
   • Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary.

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 create passed as encrypted S3_* environment variables
• Review of which home services data classes may be handled; this blueprint models public information only

Workflow Steps

1. Model the home services domain: Create the tables services, parts_stock, jobs, job_lines, events. Keep sensitive classes out of this schema.
2. Model orders with explicit status transitions and order lines.
3. Apply status changes transactionally and record an event per change.
4. Expose status history to authorized callers only.
5. Deploy and verify history and conflict rejection.
6. Run the synchronous deploy once and read the result.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Components:
  • App Server: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0
  • Managed PostgreSQL Database: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0

Limitations

• No health, financial, privacy or other compliance claim is made. Customer addresses and access instructions are personal data.
• Public content and synthetic examples only until actual data-handling requirements have been reviewed.

Examples

• Title: Laravel pattern fixture
  • Description: Verified transactional workflows basis for this blueprint.
  • Source Reference: tests/deploy-canaries/laravel-patterns

Next Actions

1. Browse the catalog index: GET /v1/catalog
2. Search published recipes: 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 Home Services: GET /v1/catalog/nodes/industry%3Ahome-services
6. Browse Order Tracking: GET /v1/catalog/nodes/workload%3Aorder-tracking
7. Browse Laravel: GET /v1/catalog/nodes/stack%3Aframework-laravel
8. Browse Deploy Web App: GET /v1/catalog/nodes/intent%3Adeploy-web-app