How oasido/shift-scheduler works
Main Components
a) Client Layer (Frontend):
• React-based frontend application
• Key modules:
• Admin Control Panel
• User Dashboard
• Authentication Components
• Schedule Views (Desktop/Mobile)
b) Server Layer (Backend):
• Node.js/Express backend
• Key components:
• Authentication Service (Passport)
• Route Controllers
• Middleware
c) Database Layer:
• MongoDB database
• Collections:
• Users
• Shifts
d) Nginx Layer:
• Reverse proxy/load balancer
• Use a proxy server symbol
Component Relationships
Client ←→ Nginx ←→ Backend ←→ MongoDB
Detailed Component Breakdown
Frontend Components (Group these in a container):
• Authentication
• Login Component
• User Features
• Schedule Viewer
• Availability Management
• Request Management
• Admin Features
• User Management
• Schedule Generation
• Request Processing
• Schedule History
Backend Components (Group these in a container):
• Authentication Services
• Route Controllers
• Middleware
• Admin Authorization
• Models
• User
• Shift
Data Flow Indicators
Following key interactions:
• User authentication flow
• Schedule creation/viewing
• Request submission/approval
• Admin management operations
Infrastructure Layer
Docker containers:
• Frontend container
• Backend container
• MongoDB container
• Nginx container
Additional Elements
• Version/environment indicators
• Security boundaries
• Scalable components