How txmmybxy/documentflowserver works
DocumentFlowServer is an ASP.NET Core document-generation backend. Its principal workflow is: a client manages templates through the API, a worker obtains generation work and template data, produces documents, then uploads results back to the API for storage and notification. The graph also preserves authentication, user/department administration, document handling, and notifications. Several controller and worker implementation details were not sampled; those links are shown only where the README or source index supports them.
Main entry points: Program.cs Web API · TemplateService.cs Template service · WorkerController.cs Worker API · ApiClient.cs API client
Components 18
API and access
- Web API
DocumentFlowServer.Api/Program.cs - Template API
DocumentFlowServer.Api/Controllers/TemplateController.cs - Worker API
DocumentFlowServer.Api/Controllers/WorkerController.cs
Business services
- Account service
DocumentFlowServer.Infrastructure/Account/AccountService.cs - Template service
DocumentFlowServer.Infrastructure/Template/TemplateService.cs - User service
DocumentFlowServer.Infrastructure/User/UserService.cs - Department service
DocumentFlowServer.Infrastructure/Department/DepartmentService.cs - Document service
DocumentFlowServer.Infrastructure/Document/DocumentService.cs - Worker task service
DocumentFlowServer.Infrastructure/Common/Services/WorkerTaskService.cs - Notification service
DocumentFlowServer.Infrastructure/Notification/NotificationService.cs
Persistence and files
- Application database
DocumentFlowServer.Infrastructure/Data/ApplicationDbContext.cs - File storage
DocumentFlowServer.Infrastructure/Common/Services/FileStorageService.cs - Redis cache
Document generation
- Background worker
DocumentFlowServer.Worker/Service/WorkerService.cs - Template generation
DocumentFlowServer.Worker/Service/DocumentTemplateService.cs - API client
DocumentFlowServer.Worker/Client/Api/ApiClient.cs
Other components
- Client
- Realtime clients
Connections 21
- Client → Web API: sends requests
README.md - Web API → Template API: routes requests
DocumentFlowServer.Api/Program.cs - Template API → Template service: calls
DocumentFlowServer.Api/Controllers/TemplateController.cs - Client → Worker API: requests work
- Worker API → Worker task service: dispatches tasks
DocumentFlowServer.Api/Controllers/WorkerController.cs - Worker API → Template service: gets template data
DocumentFlowServer.Api/Controllers/WorkerController.cs - Background worker → API client: uses client
- Background worker → Template generation: runs generation
- API client → Worker API: reports over HTTP
README.md - Template service → File storage: saves files
DocumentFlowServer.Infrastructure/Template/TemplateService.cs - Template service → Notification service: sends notices
DocumentFlowServer.Infrastructure/Template/TemplateService.cs - Template service → Redis cache: caches results
DocumentFlowServer.Infrastructure/Template/TemplateService.cs - User service → Notification service: sends notices
DocumentFlowServer.Infrastructure/User/UserService.cs - Department service → Notification service: sends notices
DocumentFlowServer.Infrastructure/Department/DepartmentService.cs - Document service → File storage: stores files
DocumentFlowServer.Infrastructure/Document/DocumentService.cs - Document service → Realtime clients: notifies client
DocumentFlowServer.Infrastructure/Document/DocumentService.cs - Web API → Realtime clients: maps hubs
DocumentFlowServer.Api/Program.cs - Account service → User service: loads user
DocumentFlowServer.Infrastructure/Account/AccountService.cs - Account service → Application database: uses account data
- API client → Web API: uploads results
README.md - Web API → Application database: configures context
DocumentFlowServer.Api/Program.cs