How srinath1987-ops/campuspro works
Project Type and Purpose
• This is a full-stack, serverless web application (“CampusPro Bus Management System”) that provides real-time bus tracking, student counting, role-based dashboards (Admin, Driver, Student), and reporting.
• Key purpose: streamline campus bus operations by tying together IoT hardware (ESP32 RFID gates), serverless endpoints (Supabase Edge/Functions), a PostgreSQL database, and a React/TypeScript front end.
File Structure
Top-level folders:
• “hardware/ESP32_RFID_Gate_Controller” – IoT firmware controlling RFID gate readers.
• “Edge Function/http_bus_entry_exit” & “Edge Function/http_bus_status” – serverless TypeScript functions for handling IoT HTTP callbacks.
• “supabase/functions” mirrors the Edge Functions for deployment under Supabase’s Functions.
• “src/” – React app with subfolders: components, contexts, hooks, integrations (Supabase client + schemas), pages (admin, driver, public), redux (state slices), utils, main.tsx.
• “scripts/create_missing_tables.sql” – DDL for relational schema.
• Configuration: vite.config.ts, tailwind.config.ts, supabase/config.toml.
Extract Architectural Insights from README
• Frontend: React + TypeScript + Tailwind, state management via Redux Toolkit.
• Backend: Supabase (PostgreSQL + Auth + Edge Functions).
• Roles and use cases: Admin, Driver, Student.
• Real-time updates (Supabase real-time or polling via Edge Functions).