juan-419/proyecto_des

Purpose and startup

AutoFix Pro is a server-rendered automotive workshop management system. It manages customers, their vehicles, mechanics, repairs, SOAT records, dashboard metrics, and reports. The FastAPI application entry point is main.py; local execution uses uvicorn main:app --reload. HTML is rendered through Jinja2 templates in templates/.

Application composition and routing

main.py assembles the FastAPI app and exposes or mounts the functional modules. Domain-oriented route handlers are separated by resource:

• Customer lifecycle: cliente.py

• Vehicle lifecycle and customer association: carro.py

• Mechanic lifecycle: mecanico.py

• Repair registration and mechanic assignment: reparacion.py

• Dashboard metrics: dashboard.py

• SOAT and reporting functions: soat.py, reporte.py

These modules form the HTTP boundary for both browser pages and the documented API-oriented repair functionality.

Persistence and domain model

models.py defines SQLModel entities, fields, relationship mappings, and the repair–mechanic link model. The central relationship graph is:

• Cliente 1:N Carro

• Carro 1:1 SOAT

• Carro 1:N Reparacion

• Reparacion N:M Mecanico

db.py owns database/session setup and is the persistence boundary used by route modules. Entities support logical deletion through an active flag rather than immediate physical removal; list and “eliminados” views separate active and inactive records.

Customer and vehicle workflow

Customer creation/editing/listing originates in cliente.py and is presented through templates/cliente_list.html, templates/cliente_carros.html, and related edit/card templates. Vehicles are created under a customer and managed through carro.py; templates/carro_list.html and templates/carro_servicios.html expose vehicle inventory and its service history. This customer → vehicle hierarchy is the primary ownership path for repairs and SOAT data.

Repair operations

reparacion.py is the operational core: it creates, edits, lists, soft-deletes, and restores repair records tied to a vehicle. It also manages the many-to-many assignment of mechanics represented in models.py. The primary UI stages are templates/reparacion_new.html, templates/reparacion_edit.html, and templates/reparacion_list.html; inactive repairs are isolated in templates/reparacion_eliminadas.html.

Presentation, dashboard, and reports

Jinja2 templates provide the browser UI, with shared layout fragments in templates/navbar.html, templates/header.html, and templates/footer.html. dashboard.py computes aggregate counts for customers, vehicles, mechanics, and active repairs, rendered by templates/dashboard.html. reporte.py is the reporting boundary, while templates/index.html provides the landing view.

External services and runtime

The application runs on Python/FastAPI with SQLModel and Jinja2; declared deployment/runtime artifacts are requirements.txt and runtime.txt, consistent with Render deployment. Supabase is used specifically for public object storage, not necessarily as the primary relational database: supa/supabase_upload.py uploads customer or vehicle images and persists their accessible URLs through the domain data layer. The README describes SQLite as the relational persistence option.