How hattivishwajeet-ctrl/disaster-relief-management-system works
Admins use the workspace to manage disasters, camps, requests, stock, allocations, and deliveries; volunteers submit field reports and update availability. The API is the main runtime entry point: it authenticates requests, performs operational actions, and serves analytics. Field reports are stored in MongoDB and reconciled into MySQL, while a WebSocket hub publishes MySQL notifications to admins. The graph follows documented capabilities where implementation excerpts are incomplete; unsampled routes are represented at the API boundary rather than given speculative call links.
Main entry points: api.mjs JSON API · workspace.jsx Operations workspace · hub.mjs Live event hub · index.mjs HTTP server
Components 18
User experience
- Operations workspace
app/workspace.jsx
Application runtime
- HTTP server
server/index.mjs - JSON API
server/api.mjs - Session security
server/security.mjs
Relief operations
- Disaster and camp setup
server/api.mjs - Request ranking
server/api.mjs - Allocation and delivery
server/api.mjs - Inventory and shortages
server/api.mjs - Volunteer availability
server/api.mjs
Reporting and live updates
- Field report intake
server/api.mjs - Report reconciliation
server/reports.mjs - Operational analytics
server/analytics.mjs - Live event hub
server/hub.mjs
Persistence
- Database adapters
server/db.mjs - MySQL operations store
- MongoDB report store
Other components
- Admin
- Volunteer
Connections 32
- Admin → Operations workspace: uses
README.md - Volunteer → Operations workspace: uses
README.md - Operations workspace → JSON API: calls
app/workspace.jsx - Operations workspace → Live event hub: opens socket
app/workspace.jsx - HTTP server → JSON API: routes requests
server/index.mjs - HTTP server → Live event hub: starts
server/index.mjs - HTTP server → Report reconciliation: starts
server/index.mjs - HTTP server → Database adapters: initializes
server/index.mjs - JSON API → Session security: authenticates
server/api.mjs - JSON API → Database adapters: queries
server/api.mjs - JSON API → Disaster and camp setup: handles
server/api.mjs - JSON API → Request ranking: handles
server/api.mjs - JSON API → Allocation and delivery: handles
server/api.mjs - JSON API → Inventory and shortages: handles
server/api.mjs - JSON API → Volunteer availability: handles
README.md - JSON API → Field report intake: handles
server/api.mjs - JSON API → Operational analytics: queries
server/api.mjs - JSON API → Report reconciliation: reads summaries
server/api.mjs - Request ranking → MySQL operations store: updates priority
server/api.mjs - Allocation and delivery → MySQL operations store: allocates stock
server/api.mjs - Inventory and shortages → MySQL operations store: updates stock
server/api.mjs - Volunteer availability → MySQL operations store: stores status
- Field report intake → MongoDB report store: stores reports
README.md - Report reconciliation → MongoDB report store: watches reports
server/reports.mjs - Report reconciliation → MySQL operations store: reconciles reports
server/reports.mjs - Operational analytics → MySQL operations store: queries metrics
server/analytics.mjs - Live event hub → Session security: checks sessions
server/hub.mjs - Live event hub → MySQL operations store: polls notifications
server/hub.mjs - Database adapters → MySQL operations store: connects
server/db.mjs - Database adapters → MongoDB report store: connects
server/db.mjs - JSON API → Operations workspace: returns data
app/workspace.jsx - Live event hub → Operations workspace: publishes events
README.md