ishan1o1/location_tracker

Purpose and System Shape

This is a client/server location-oriented application with authentication, user profiles, a dashboard map, REST APIs, persistence, and real-time socket handling. The frontend is a Vite/React single-page client; the backend is a Node.js HTTP service organized around routes, controllers, services, models, and middleware.

Frontend Entry and UI Composition

The browser entry point is client/src/main.jsx, which mounts the application defined in client/src/App.jsx. Page-level flows are separated into login, dashboard, and profile views:

• client/src/pages/LoginPage.jsx

• client/src/pages/Dashboard.jsx

• client/src/pages/ProfilePage.jsx

The dashboard’s defining UI boundary is the location/map experience, composed from client/src/component/Map.jsx, client/src/component/Sidebar.jsx, and client/src/component/UserCard.jsx.

Client API, Auth, and Real-Time Boundary

HTTP communication is centralized under the client service layer:

• client/src/services/api.js

• client/src/services/authService.js

This layer should isolate API base URL, request configuration, and authentication-oriented calls from UI components. Runtime environment values are exposed through client/src/config/env.js and the template client/.env.example.

Real-time connectivity is distinct from REST calls through client/src/socket.js; map/dashboard state can consume socket events without coupling directly to request services.

Server Entry and Request Pipeline

server/server.js is the backend composition and process entry point. It connects infrastructure, mounts route modules, configures middleware, and initializes the socket subsystem.

Request flow is expected to follow:

1. Client calls an auth or location endpoint.

2. A route selects the controller.

3. Protected operations pass through auth middleware.

4. Controllers delegate business logic or persistence.

5. Responses return through the HTTP boundary.

The main route boundaries are:

• server/routes/authRoutes.js

• server/routes/locationRoute.js

• server/middleware/authMiddleware.js

Identity and Authorization

Authentication is split between transport/controller responsibilities and reusable service logic:

• server/controllers/authController.js

• server/services/authService.js

• server/utils/jwt.js

server/models/User.js defines the persisted user-domain boundary. JWT generation/validation is intentionally separated from controller code, while server/middleware/authMiddleware.js protects downstream location or profile-related operations.

Location and Real-Time Updates

Location-specific HTTP operations are handled by:

• server/routes/locationRoute.js

• server/controllers/locationController.js

The real-time counterpart is server/socketHandler.js. This establishes a separate event-driven control path for live updates, likely allowing connected clients to receive location/user changes without polling. The frontend map and the backend socket handler are the key boundary for this feature, mediated by client/src/socket.js.

Infrastructure and Deployment

Database initialization is isolated in server/config/database.js; its concrete provider is not identifiable from the supplied tree. Server diagnostics are centralized in server/logger.js.

The client is configured for Vite development/build output through client/vite.config.js and includes Vercel deployment configuration in client/vercel.json. Environment-dependent values should remain outside source control, using the provided client environment template and corresponding server runtime configuration.