How deflegmator666/espnodeserver works
This is a small Express server for logging in and managing device events. A client request enters through the server and router; data routes pass through cookie-token authentication before event handlers create, list, or delete entries in a process-local array. Login issues JWTs, while a role-checking middleware exists but is not applied to the routes shown. The excerpts do not establish persistence beyond memory or any external service integrations.
Main entry points: routes/index.js API router · index.js Express server · eventController.js Event handlers · authMiddleware.js Cookie auth
Components 8
HTTP routing
- Express server
index.js - API router
routes/index.js
Identity and access
- Cookie auth
middleware/authMiddleware.js - Login and JWT
controllers/userController.js - Role guard
middleware/checkRoleMiddleware.js
Event handling
- Event handlers
controllers/eventController.js - Event array
cashDataArray/dataArr.js
Other components
- API client
Connections 6
- API client → Express server: sends requests
- Express server → API router: mounts routes
index.js - API router → Cookie auth: guards data routes
routes/index.js - API router → Event handlers: dispatches data routes
routes/index.js - API router → Login and JWT: dispatches login
routes/index.js - Event handlers → Event array: reads and updates
controllers/eventController.js