How mo7amedrabei14-cell/eoc-system works
This is an emergency-operations coordination application: staff sign in, then use a dashboard to work with missions and related operational records. The backend also provides user, volunteer, and branch management, with permission checks and PostgreSQL access; the monolithic API contains additional radar, weather, and local-news functionality. The graph distinguishes those domains and includes frontend health/error handling. README content was unavailable, and several core frontend modules were not sampled, so their internal behavior and most frontend-to-API links are not inferred.
Main entry points: main.py Operations API · Login.jsx Sign in · dependencies.py Request dependencies · missions.py Mission operations
Components 22
Web application
- App bootstrap
frontend/src/main.jsx - App routes
frontend/src/App.jsx - Sign in
frontend/src/Login.jsx - Operations dashboard
frontend/src/Dashboard.jsx - Segment inputs
frontend/src/SegInputs.jsx - API base config
frontend/src/apiBase.js - Server health UI
frontend/src/serverHealth.jsx - Health checks
frontend/src/serverHealthCore.js - Client error reporting
frontend/src/clientErrorReport.js - Workspace state
frontend/src/workspace.js
API and operations
- Operations API
main.py - Mission operations
routers/missions.py - User administration
routers/users.py - Volunteer registry
routers/volunteers.py - Branch directory
routers/branches.py - Realtime events
realtime.py - Audit logging
audit.py
Identity and access
- Request dependencies
dependencies.py - Authentication and permissions
auth.py
Persistence
- Database connections
db.py - PostgreSQL
Other components
- Operations staff
Connections 32
- Operations staff → Sign in: signs in
frontend/src/Login.jsx - Operations staff → Operations dashboard: uses
- App bootstrap → App routes: loads
frontend/src/main.jsx - App routes → Sign in: routes to
frontend/src/App.jsx - App routes → Operations dashboard: routes to
frontend/src/App.jsx - Sign in → Operations API: requests token
frontend/src/Login.jsx - Sign in → API base config: uses base
frontend/src/Login.jsx - Sign in → Server health UI: renders
frontend/src/Login.jsx - Sign in → Health checks: checks health
frontend/src/Login.jsx - Server health UI → Health checks: uses
frontend/src/serverHealth.jsx - Health checks → API base config: uses base
frontend/src/serverHealthCore.js - App bootstrap → Client error reporting: installs reporting
frontend/src/main.jsx - Operations API → Mission operations: routes to
main.py - Operations API → User administration: routes to
main.py - Operations API → Volunteer registry: routes to
main.py - Operations API → Branch directory: routes to
main.py - Operations API → Realtime events: uses
main.py - Operations API → Audit logging: uses
main.py - Operations API → Database connections: uses
main.py - Mission operations → Request dependencies: depends on
routers/missions.py - User administration → Request dependencies: depends on
routers/users.py - Volunteer registry → Request dependencies: depends on
routers/volunteers.py - Branch directory → Request dependencies: depends on
routers/branches.py - Mission operations → Audit logging: records actions
routers/missions.py - Request dependencies → Authentication and permissions: checks identity
dependencies.py - Request dependencies → Database connections: gets connection
dependencies.py - Authentication and permissions → Database connections: queries
auth.py - Mission operations → PostgreSQL: reads and writes
routers/missions.py - User administration → PostgreSQL: reads and writes
routers/users.py - Volunteer registry → PostgreSQL: reads and writes
routers/volunteers.py - Branch directory → PostgreSQL: reads
routers/branches.py - Database connections → PostgreSQL: connects