page:blueprints:home services:product catalog:django

Home services: product catalog using Django

Summary

A product catalog blueprint for home services built with Django 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 from, service areas and hours, licensing and insurance summary.

Technical Basis

Verified on Django: 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: product catalog using Django
• Where can I host Home services: Product catalog built with Django?
• I need a genuinely specialized product catalog workflow covering service areas, job materials, and field-job status.

Resource Requirements

• Compute
• Postgres
• 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.

Framework

Django

Workload

Product catalog

Industry

Home services

Release Status

Published

Support Status

Verified

Execution Status

Ready

Prerequisites

• A Django project (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 template)
• A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted)
• Bucket credentials from ample bucket create passed as encrypted S3_* environment variables
• A review of which home services data classes may be handled at all; this blueprint models public information only

Tested Configuration

• Template: python-3.12
• Runtime: python
• Size: s-1vcpu-1gb
• Install: python3 -m pip install --target .ample/python -r requirements.txt
• Start: PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py

Workflow Steps

1. Model the home services domain: Create the tables services, parts_stock, jobs, job_lines, events. Service catalog as skus lives in services; keep the sensitive classes (customer addresses and access notes, payment 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.
7. Verify: Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the home services workflow.

Examples

• Django pattern fixture: Verified transactional workflows basis for this blueprint.

Success Checks

1. App responds on its public URL.
2. Transactional-workflows self-test from the example.

Limitations

• Customer addresses and access instructions are personal data; keep them out until handling is reviewed.
• Verified on the python-3.12 template at s-1vcpu-1gb; region, request-duration limits, and other sizes are unknown or unverified.

Cost Estimate

• Monthly Amount: $10.00
• Basis: Size prices from pricing.toml (loaded by the API).

Evidence Summary

• Django pattern fixture deployed on Ample: The transactional workflows checks passed.

Last Verified At

2026-09-20T03:31:44Z

Next Actions

1. Browse the catalog index.
2. Search published recipes by intent, stack, and constraints.
3. Prepare a side-effect-free deployment plan for an authorized project.