How dymproject/purest-admin works
Project Type and Purpose
• This is a full-stack, truly front-end/back-end separated “Purest Admin” system.
• Back end: .NET 8 Web API built on a streamlined ABP-style modular framework, using SqlSugar for data access, a custom workflow engine, SignalR for real-time features, and background workers.
• Front end: a Vue3/Vite SPA (client-vue/pure-admin) and a WPF desktop client (client-wpf) that both consume the HTTP API.
• It targets RBAC-based permission management and is designed as a template for rapid secondary development.
File Structure Highlights
• api/…
• PurestAdmin.Api.Host: HTTP host and middleware (authentication, exception filters, routing)
• PurestAdmin.Application: application services (Auth, User, Role, Workflow, etc.)
• PurestAdmin.Core: cross-cutting concerns (caching, encryption, file storage, SignalR extensions)
• PurestAdmin.SqlSugar: data layer (entities, repositories, DB connection)
• PurestAdmin.Workflow: workflow engine modules and definition/instance services
• PurestAdmin.Multiplex: SignalR hubs and event-bus subscribers
• PurestAdmin.BackgroundService: long-running background jobs (email, auditing, notifications)
• PurestAdmin.Zero: code-generation and data seed templates
• client-vue/pure-admin/: Vue3 SPA
• client-wpf/: WPF/Prism desktop client
• screenshot/: UI mock-ups
Key Architecture Principles
• Strict separation of UI and API: clients know nothing about specific routes; they fetch “feature codes” from the API and mount UI routes/permissions at runtime.
• Modular server architecture: each module (Auth, Workflow, Data, Multiplex, Background) is an independent ABP module.
• Single-token silent refresh: custom JWT middleware handles refresh without a separate refresh token.
• Event-driven and real-time: SignalR hubs for online user updates, event bus for background processing.
• Workflow engine: roadmap of workflow definitions → execution → instance management.