How ragavryan365/student-tracker-backend works
This is a small Express backend for student tracking. Its main workflow fetches a class code and that class’s students, then supports subject listing, attendance verification, and attendance marking through PostgreSQL repositories. The route handlers and repository calls are shown in the sampled source; the README documents the database domain tables. No separate authentication or faculty-facing client is evidenced, so the initiating actor is represented generically.
Main entry points: readDBRepo.js Read operations · connectDB.js Connection pool · server.js Class students · writeDBRepo.js Write operation
Components 9
API routes
- Class students
src/server.js - Subject list
src/server.js - Verify attendance
src/server.js - Mark attendance
src/server.js
Database repositories
- Read operations
src/repositories/readDBRepo.js - Write operation
src/repositories/writeDBRepo.js
Persistence
- Connection pool
src/config/connectDB.js
Other components
- API client
- PostgreSQL
Connections 11
- API client → Class students: requests students
src/server.js - API client → Subject list: requests subjects
src/server.js - API client → Verify attendance: checks attendance
src/server.js - API client → Mark attendance: submits attendance
src/server.js - Class students → Read operations: looks up class and students
src/server.js - Subject list → Read operations: loads subjects
src/server.js - Verify attendance → Read operations: checks records
src/server.js - Mark attendance → Write operation: inserts attendance
src/server.js - Read operations → Connection pool: queries
src/repositories/readDBRepo.js - Write operation → Connection pool: inserts through
src/repositories/writeDBRepo.js - Connection pool → PostgreSQL: connects to
src/config/connectDB.js