How cth-sla/devicerepairmanager works
DeviceRepairManager is a device-repair operations application. Staff sign in, then manage organizations, customers and devices alongside repair tickets and warranty cases; a separate public registration flow collects service-support requests that staff can review and update. Dashboard and statistics provide operational views. The React pages use shared storage/API services, with server-side local storage and MySQL support; the client can also route requests to the Hostinger PHP backend. The README is empty, and unsampled page/backend details limit some wiring shown here.
Main entry points: App.tsx App routing · client.ts API client · server.ts Node API · storage.ts Storage service
Components 21
Application access
- App routing
App.tsx - Session and auth
contexts/AuthContext.tsx - Login
pages/Login.tsx - Dashboard
pages/Dashboard.tsx - Statistics
pages/Statistics.tsx
Repair operations
- Organizations
pages/Organizations.tsx - Customers
pages/Customers.tsx - Devices
pages/Devices.tsx - Repair tickets
pages/Repairs.tsx - Warranty cases
pages/Warranty.tsx
Service support
- Public registration
pages/ServiceRegisterPage.tsx - Registration form
components/ServiceRegisterCard.tsx - Service requests
pages/Services.tsx
API and persistence
- Storage service
services/storage.ts - API client
services/client.ts - Node API
server.ts - Hostinger API
public/hostinger_api.php - MySQL
- Local store
data/db_store.json
Other components
- Staff
- Public requester
Connections 22
- Staff → App routing: opens
- Public requester → App routing: opens
- App routing → Session and auth: provides session
- App routing → Login: routes
- App routing → Dashboard: routes
- App routing → Statistics: routes
- App routing → Organizations: routes
- App routing → Customers: routes
- App routing → Devices: routes
- App routing → Repair tickets: routes
- App routing → Warranty cases: routes
- App routing → Public registration: routes
- App routing → Service requests: routes
- Public registration → Storage service: submits through
- Service requests → Storage service: manages requests
- Session and auth → API client: checks health
- Storage service → API client: sends API requests
- API client → Node API: requests
- API client → Hostinger API: fallback requests
- Node API → MySQL: reads and writes
- Node API → Local store: persists fallback
- Hostinger API → MySQL: reads and writes