How eugleo/request2-service works
Main System Components
a) Frontend Layer:
• React-based web application (from the frontend submodule)
• Form rendering system for custom request types
• User interface for request management and tracking
b) Backend Layer:
• Haskell-based API server
• Authentication/Authorization system
• Email notification service (using ssmtp)
c) Storage Layer:
• PostgreSQL database for request data and user information
• File storage system for uploaded files
External Dependencies
• Mail server (SMTP) for notifications
• Docker container environment
[Client Browser] → [Frontend (React)] → [Backend (Haskell)] → [Storage]
User form submission flow
Client → Frontend → Backend → Database
File upload flow
Client → Frontend → Backend → File Storage
Notification flow
Backend → SMTP Server → User Email
Important Subsystems
a) Form Management:
• Relationship between RequestTypes directory and frontend form rendering
• How custom forms are compiled and served
b) Request Processing:
• Workflow of request creation, tracking, and updates
• Changelog system
c) Authentication Flow:
• Token-based authentication system
• Password reset flow
Configuration Components
A section showing configuration dependencies:
• request2.cfg (backend configuration)
• ssmtp.conf (email configuration)
• Docker configuration
Specific Details
Annotations for:
• Port 8080 for backend service
• Mounted storage at /srv/data
• Database connection
• Email notification system
Integration Points
Clearly mark:
• API endpoints between frontend and backend
• Database connection points
• File storage mount points
• Email service integration