How mohdsaadma07/arrive works
Project Type & Purpose
• Arrive is a full-stack MERN (MongoDB, Express, React, Node.js) web application for secure attendance tracking using facial recognition (face-api.js), geolocation (Leaflet), automated email alerts (Nodemailer/SMTP), and Firebase authentication.
Key Architectural Components
a. Frontend (React + face-api.js + Firebase Auth + Leaflet)
– Pages: Login, TeacherDashboard, StudentDashboard, AttendanceDashboard, AttendanceSummary, VerifyAttendance
– Services: authServices.js (wraps Firebase Auth), face recognition models in /public/models
– UI layer calls backend APIs via HTTP (axios/fetch)
b. Backend (Node.js + Express + JWT + Firebase Admin)
– Routes & Controllers:
• /api/users → userController
• /api/sessions → sessionController
• /api/attendance → attendanceController & attendanceSummary
– Middleware: authMiddleware (validates JWT / Firebase token)
– Services: firebaseAdmin.js (verifies Firebase tokens), mail.js (Nodemailer SMTP)
– Helpers: geo.js (calculates geolocation constraints)
c. Database & Storage
– MongoDB Atlas (Mongoose models: User, Session, Attendance)
– face-api.js model files served from client/public/models
d. External Services
– Firebase Authentication (OAuth + JWT issuance)
– SMTP Email Provider (Gmail/SMTP)
– Leaflet/OpenStreetMap for geolocation maps
Relationships & Data Flows
1) User opens React app → authenticates via Firebase Auth → receives JWT
2) Client calls Express API (/user, /session, /attendance) attaching JWT → authMiddleware verifies via firebaseAdmin
3) For marking attendance: React invokes face-api.js locally to capture & verify face → if success and within time/geofence (geo.js), calls /attendance → server saves record in MongoDB
4) Teachers generate sessions via /session → stored in DB → students fetch session list
5) attendanceSummary controller aggregates data → real-time dashboards update via polling or websockets (if implemented)
6) mail.js triggers SMTP email alerts when attendance thresholds fall below configured limits
Architectural Patterns & Principles
• Layered architecture:
• Presentation (React)
• Service/API (Express controllers + middleware + services)
• Data (MongoDB via Mongoose)
• Separation of concerns: face recognition and geolocation done client-side; business logic and persistence server-side
• JWT-based security with token validation middleware