How alexcrazy42/fithub works
FitHub is a fitness-industry SaaS platform combining gym operations (ERP), visitor-facing messaging (CRM), and marketplace features; a separate BankManager handles payment intents. The main user journey is using the React app to access platform capabilities through its API, with domain services and persistence behind that API. Groups preserve documented capabilities even where source was not sampled. Relationships between unsampled subsystems are omitted; dashed links mark the unverified app-to-API entry path.
Main entry points: src React app · Web Platform API · Messaging Messaging and chat · Message.cs Message domain
Components 20
User experience
- React app
frontend/src
Fitness platform
- Platform API
backend/Platform/src/Web - Users and access
backend/Platform/src/Application/Users - Gyms and equipment
backend/Platform/src/Application/Equipments - Training management
backend/Platform/src/Application/Trainings - Messaging and chat
backend/Platform/src/Application/Messaging - Message domain
backend/Platform/src/Domain/Messaging/Message.cs - File services
backend/Platform/src/Application/Files - Video services
backend/Platform/src/Application/Videos
Commerce and payments
- Marketplace
backend/Platform/src/Application/Marketplace - BankManager API
backend/BankManager/src/Web - Payment intents
backend/BankManager/src/Application/Payments/PaymentIntentService.cs - Payment domain
backend/BankManager/src/Domain/PaymentIntent.cs - Payment workers
backend/BankManager/src/Jobs
Shared infrastructure
- Platform data layer
backend/Platform/src/Data - BankManager data
backend/BankManager/src/Data/BankManagerDataContext.cs - RabbitMQ messaging
backend/Common/RabbitMQ
Technology sandbox
- Technology experiments
sandbox
Other components
- Platform user
- S3 object storage
Connections 11
- Platform user → React app: uses
- React app → Platform API: calls API
- Platform API → Messaging and chat: uses sticker service
backend/Platform/src/Web/V1/Messaging/StickerController.cs - Message domain → Platform data layer: persists
- Marketplace → BankManager API: requests payments
- Payment intents → Payment domain: updates intent
- Payment domain → BankManager data: persists
backend/BankManager/src/Data/BankManagerDataContext.cs - Payment workers → Payment intents: processes intents
- File services → S3 object storage: stores files
- Video services → S3 object storage: stores video
- Messaging and chat → Message domain: uses messages