How lele97/carmaintenance works
CarMaintenance records vehicle maintenance and presents a dashboard for browsing history, costs, and reminders. The server-rendered workflow routes browser requests through Express to maintenance handlers, validates submissions, persists MongoDB-backed records, and renders Pug pages or JSON. Production also supports a browser-local storage mode with CRUD, statistics, filtering, and export; that client-side branch is documented and represented by its JavaScript modules, though their internal call wiring was not sampled. The diagram focuses on relationships evidenced by excerpts or README; client-side connections are left unverified.
Main entry points: interventionService.js Intervention service · app.js Express application · index.js Dashboard route · add.js Add route
Components 20
Web interface
- Express application
app.js - Dashboard route
routes/index.js - Add route
routes/add.js - Update route
routes/update.js - REST API
routes/api.js - Data endpoints
routes/data.js - Delete route
routes/delete.js - Pug pages
views
Maintenance domain
- Payload validation
utils/validator.js - Intervention service
services/interventionService.js - Stats and reminders
services/interventionService.js - Intervention schema
models/Intervention.js
Persistence modes
- Storage mode selector
utils/storageMode.js - MongoDB connection
config/database.js - MongoDB
Browser application
- Dashboard interactions
public/javascripts/dashboard.js - Browser storage
public/javascripts/storage.js - Mileage readings
public/javascripts/mileageReadings.js
Other components
- Car owner
- Browser
Connections 31
- Browser → Express application: sends requests
app.js - Express application → Dashboard route: routes requests
app.js - Express application → Add route: routes requests
app.js - Express application → Update route: routes requests
app.js - Express application → REST API: routes requests
app.js - Express application → Data endpoints: routes requests
app.js - Express application → Delete route: routes requests
app.js - Dashboard route → Intervention service: queries records
routes/index.js - Dashboard route → Stats and reminders: calculates dashboard
routes/index.js - Dashboard route → Pug pages: renders dashboard
routes/index.js - Add route → Payload validation: validates input
routes/add.js - Add route → Intervention service: creates records
routes/add.js - Add route → Pug pages: renders form
routes/add.js - Update route → Payload validation: validates input
routes/update.js - Update route → Intervention service: reads and updates
routes/update.js - Update route → Pug pages: renders edit
routes/update.js - REST API → Payload validation: validates input
routes/api.js - REST API → Intervention service: manages records
routes/api.js - Data endpoints → Intervention service: queries records
routes/data.js - Data endpoints → Stats and reminders: exports statistics
routes/data.js - Delete route → Intervention service: deletes records
routes/delete.js - Intervention service → Intervention schema: queries and writes
services/interventionService.js - Intervention service → MongoDB connection: checks connection
services/interventionService.js - Intervention schema → MongoDB: persists records
- Dashboard route → Storage mode selector: selects mode
routes/index.js - REST API → Storage mode selector: reports mode
routes/api.js - MongoDB connection → MongoDB: connects
config/database.js - Browser → Dashboard interactions: uses dashboard
- Dashboard interactions → Browser storage: uses local CRUD
- Dashboard interactions → Mileage readings: uses readings
- Browser storage → Browser: stores locally