How yash-ranjan-124/electron_notifier works
This is an Express/Mongoose event-notifier backend, despite the README’s “Electron Based” title; the shown code exposes HTTP APIs and Socket.IO, not an Electron client. The main workflow accepts an event through the HTTP routes, persists it, then looks up users interested in its category and emits a notification to their email-named socket rooms. Account and category APIs are separate branches. Edges reflect shown calls or SOURCE INDEX references; the event service’s use of the Socket.IO server is visible, but its connection to app-level initialization is not, so that link is dashed.
Main entry points: app.js Express app · index.js API routes · event.js Event service · socketIOHandler.js Socket.IO handler
Components 17
HTTP entry
- Express app
app.js - API routes
routes/index.js - User controller
controllers/user.controller.js - Event controller
controllers/event.controller.js - Category controller
controllers/eventCategory.controller.js
Domain services
- User service
services/user.js - Event service
services/event.js - Category service
services/eventsCategory.js
Mongo data
- User model
models/user.js - Event model
models/event.js - Category model
models/eventCategory.js - MongoDB
- Mongo connector
libs/mongoHandler.js
Realtime delivery
- Socket.IO handler
libs/socketIOHandler.js
Other components
- API user
- API client
- Socket client
Connections 17
- API client → Express app: sends HTTP
app.js - Express app → API routes: mounts routes
app.js - API routes → User controller: routes requests
routes/index.js - API routes → Event controller: routes requests
routes/index.js - API routes → Category controller: routes requests
routes/index.js - User controller → User service: calls
controllers/user.controller.js - Event controller → Event service: calls
controllers/event.controller.js - Category controller → Category service: calls
controllers/eventCategory.controller.js - User service → User model: queries and saves
services/user.js - Event service → Event model: queries and saves
services/event.js - Event service → User model: finds interested users
services/event.js - Category service → Category model: uses model
services/eventsCategory.js - Express app → Mongo connector: connects
app.js - Mongo connector → MongoDB: opens connection
libs/mongoHandler.js - Express app → Socket.IO handler: starts server
app.js - Event service → Socket.IO handler: emits notifications
- Socket client → Socket.IO handler: joins room
libs/socketIOHandler.js