How taisabigailchuangallardo-cmd/sistema_de_reparacion works
This is a web-based workshop management system. Staff use the browser modules to manage customers and equipment, service orders through repair and delivery, inventory, technicians, payments, and management indicators. Requests pass through the REST API to route handlers and business services, which use domain entities and repositories to enforce rules and persist data. The README describes further capabilities, including access profiles, messages, and financial indicators; some implementations were not sampled, so uncertain internal links are omitted.
Main entry points: app.js Web app shell · api.js API client · ui.js UI helpers · routes.js API router
Components 21
Web application
- Web app shell
public/js/app.js - API client
public/js/api.js - UI helpers
public/js/ui.js - Customers and equipment
public/js/modulos/clientes.js - Service orders
public/js/modulos/ordenes.js - Inventory
public/js/modulos/inventario.js - Technicians
public/js/modulos/personal.js - Reports
public/js/modulos/reportes.js - Dashboard
public/js/modulos/tablero.js
HTTP API
- HTTP server
src/server.js - API router
src/http/routes.js - Authentication
src/http/autenticacion.js - Error handling
src/http/errores.js - Feature routes
src/routes
Business logic
- Use-case services
src/services/index.js
Persistence
- Repositories
src/repositories - MySQL connection pool
src/db/pool.js
Domain model
- Domain entities
src/domain - Order state rules
src/domain/base/vocabulario.js
Other components
- Workshop staff
- MySQL database
Connections 30
- Workshop staff → Web app shell: uses
- Web app shell → Customers and equipment: loads
public/js/app.js - Web app shell → Service orders: loads
public/js/app.js - Web app shell → Inventory: loads
public/js/app.js - Web app shell → Technicians: loads
public/js/app.js - Web app shell → Reports: loads
public/js/app.js - Web app shell → Dashboard: loads
public/js/app.js - Customers and equipment → API client: requests through
public/js/modulos/clientes.js - Service orders → API client: requests through
public/js/modulos/ordenes.js - Inventory → API client: requests through
public/js/modulos/inventario.js - Technicians → API client: requests through
public/js/modulos/personal.js - Reports → API client: requests through
public/js/modulos/reportes.js - Dashboard → API client: requests through
public/js/modulos/tablero.js - Customers and equipment → UI helpers: renders with
public/js/modulos/clientes.js - Service orders → UI helpers: renders with
public/js/modulos/ordenes.js - Inventory → UI helpers: renders with
public/js/modulos/inventario.js - Technicians → UI helpers: renders with
public/js/modulos/personal.js - Reports → UI helpers: renders with
public/js/modulos/reportes.js - Dashboard → UI helpers: renders with
public/js/modulos/tablero.js - API client → API router: sends HTTP requests
public/js/api.js - HTTP server → API router: mounts
src/server.js - API router → Authentication: uses
src/http/routes.js - API router → Feature routes: mounts
src/http/routes.js - API router → Error handling: handles errors with
src/http/routes.js - Feature routes → Use-case services: delegates to
src/routes/clientes.js - Use-case services → Repositories: uses
src/services/index.js - Use-case services → Domain entities: validates and updates
src/services/index.js - Repositories → MySQL connection pool: queries through
src/repositories/RepositorioBase.js - MySQL connection pool → MySQL database: queries
src/db/pool.js - Domain entities → Order state rules: uses shared vocabulary
src/domain/Cliente.js