How superfier/fibertrack works
Project type and purpose
• This is a full-stack web application (“FIBERTRACK”) comprising:
• A React-based single-page frontend (folder: optifiber) built with Vite.
• A Node.js/Express REST API backend (folder: OptifiberAPI) using MongoDB.
• Purpose: Manage fiber-optic clients—authentication, client profiles, documents, notes, payments, tickets, service packages, plus map integration and email recovery.
File structure
• Top-level separation:
• optifiber/ → Frontend SPA
• OptifiberAPI/ → Backend API
• Backend structure follows MVC-ish:
• src/controllers → request handlers per resource (auth.client.document…)
• src/middlewares → route definitions and access control
• src/models → Mongoose schemas (clients, tickets, payments…)
• src/libs → cross-cutting utilities (CORS, multer for file uploads, nodemailer)
• src/db_conn.js → MongoDB connection
• src/server.js → Express app bootstrap
• storage/img → persisted client-uploaded files
• src/templates → HTML email and index templates
• Frontend structure is component-driven:
• src/components/auth, clients, fragments, home, payments, profile, services packages, tickets
• Custom hooks (apiRequest), maps integration, CSS modules for scoping.
• vite.config.js + public assets.
Insights from README
• Environment variables control API base URL, Google Maps API key, MongoDB URI, JWT secret, email password.
• Two processes run concurrently: npm run dev in optifiber (Vite server) and in optifiberAPI (nodemon/Express).