page:blueprints:construction contractors:public directory:django

Construction contractors: public directory using Django

A public directory blueprint for construction contractors built with Django on Ample. Domain schema:

• listings (reference, project_type, location, publishing_status, agency_id): showcase projects with publishing status;
• agencies (name, license_number, service_region): branches or divisions;
• vendors (name, trade, agency_id, prequalified): subcontractors and suppliers per branch;
• reports (agency_id, period, object_key, generated_at): branch progress reports;
• state_transitions (record_type, from_state, to_state): the allowed state machine.

Public information: published project showcases, services and regions, licenses and insurance summary. Kept out of scope until handling is reviewed: site safety incidents, bid pricing, client contracts. Safety and bid data are confidential; only published showcases and branch reporting are modeled.

Technical basis verified on Django: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true).

Representative Queries

1. Construction contractors: public directory using Django
2. Where can I host Construction contractors: Public directory built with Django?
3. I need a genuinely specialized public directory workflow covering project/vendor relationships, job progress and project reporting.

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.
• CDN: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

Workflow Steps

1. Model the construction contractors domain: Create the tables listings, agencies, vendors, reports, state_transitions. Showcase projects with publishing status lives in listings; keep the sensitive classes (site safety incidents, bid pricing, client contracts) out of this schema.
2. Model listings with a publishing_status state machine scoped to the agency.
3. Serve only published listings, with media from the CDN bucket.
4. Enforce the agency scope on every query.
5. Deploy and verify a published listing and that unpublished listings are absent.
6. Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
7. Run the pattern self-test(s) from the example (/p/relational-records) and your own acceptance checks for the construction contractors workflow.

Limitations

• The technical basis (relational records on Django) was verified with the pattern fixture; the construction contractors 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. Safety and bid data are confidential; only published showcases and branch reporting are modeled.
• Verified on the python-3.12 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Authoritative: true
• 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
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.