How monoxti/monoxproperty works
Monox Property is a property-management application for managing properties, tenants, leases, expenses, rent payments, and financial reporting. Users navigate the React client to maintain records, track payments, and view reports; the client communicates with an ASP.NET Core API whose domain services process requests and persist data through Entity Framework. The README also documents JWT authentication and role-based access. Some client-to-API wiring and unsampled service internals are not shown, so those relationships are omitted unless documented.
Main entry points: App.jsx React client · ApplicationDbContext.cs Entity Framework context · PaymentController.cs Payment API · AuthController.cs Authentication API
Components 21
Web client
- React client
Monokoane Property/Client/src/App.jsx - Sign-in pages
Monokoane Property/Client/src/Pages - Property pages
Monokoane Property/Client/src/Pages - Tenant pages
Monokoane Property/Client/src/Pages - Lease pages
Monokoane Property/Client/src/Pages - Payments and reports
Monokoane Property/Client/src/Pages
API workflows
- Authentication API
Monokoane Property/Controllers/AuthController.cs - Property API
Monokoane Property/Controllers/PropControllers.cs - Tenant API
Monokoane Property/Controllers/TenantController.cs - Lease API
Monokoane Property/Controllers/LeaseController.cs - Expense API
Monokoane Property/Controllers/ExpenseController.cs - Payment API
Monokoane Property/Controllers/PaymentController.cs - Report API
Monokoane Property/Controllers/ReportController.cs
Domain services
- Authentication service
Monokoane Property/Models/Services/AuthService.cs - Property service
Monokoane Property/Models/Services/PropertyService.cs - Tenant service
Monokoane Property/Models/Services/TenantService.cs - Payment and tracking
Monokoane Property/Models/Services/PaymentService.cs - Reporting and export
Monokoane Property/Models/Services/PropertyReportService.cs
Persistence
- User repository
Monokoane Property/Models/Repo/UserRepo.cs - Entity Framework context
Monokoane Property/Models/ApplicationDbContext.cs
Other components
- Property user
Connections 24
- Property user → React client: uses
- React client → Sign-in pages: routes to
Monokoane Property/Client/src/App.jsx - React client → Property pages: routes to
Monokoane Property/Client/src/App.jsx - React client → Tenant pages: routes to
Monokoane Property/Client/src/App.jsx - React client → Lease pages: routes to
Monokoane Property/Client/src/App.jsx - React client → Payments and reports: routes to
Monokoane Property/Client/src/App.jsx - React client → Authentication API: calls REST API
- React client → Property API: calls REST API
- React client → Tenant API: calls REST API
- React client → Lease API: calls REST API
- React client → Expense API: calls REST API
- React client → Payment API: calls REST API
- React client → Report API: calls REST API
- Authentication API → Authentication service: delegates to
Monokoane Property/Controllers/AuthController.cs - Authentication service → User repository: reads and creates
Monokoane Property/Models/Services/AuthService.cs - Property API → Property service: delegates to
Monokoane Property/Controllers/PropControllers.cs - Tenant API → Tenant service: delegates to
Monokoane Property/Controllers/TenantController.cs - Lease API → Entity Framework context: service wiring unknown
- Expense API → Entity Framework context: service wiring unknown
- Payment API → Payment and tracking: delegates to
Monokoane Property/Controllers/PaymentController.cs - Payment API → Entity Framework context: reads properties
Monokoane Property/Controllers/PaymentController.cs - Report API → Reporting and export: delegates to
Monokoane Property/Controllers/ReportController.cs - Payment and tracking → Entity Framework context: queries and writes
Monokoane Property/Models/Services/PaymentService.cs - Reporting and export → Entity Framework context: stores and reads reports
Monokoane Property/Models/Services/PropertyReportService.cs