How materkey/white-label-builder works
Main Components Identification
a) Frontend Layer:
• React/Redux application (static_src directory)
• Material UI components
• WebSocket client (Centrifugo client)
b) Backend Layer:
• Django web server
• Authentication system (VK OAuth2)
• REST API endpoints
• WebSocket server (Centrifugo)
c) Task Processing Layer:
• Celery workers
• Redis (message broker & result backend)
d) Build System:
• Android app builder
• Gradle build system
• Resource customization system
Component Relationships
a) Data Flow:
• User → Frontend → Backend → Celery Workers → Android Builder
• WebSocket real-time updates: Centrifugo → Frontend
• Authentication flow: Frontend → VK OAuth2 → Backend
b) Key Dependencies:
• Celery ↔ Redis
• Django ↔ Celery
• Frontend ↔ Centrifugo
• Backend ↔ Centrifugo
Specific Elements
a) Client Side:
[Browser]
• React/Redux App
• Material UI Components
• WebSocket Client
b) Server Side:
[Django Backend]
• REST API
• Authentication
• Task Management
c) Processing:
[Build System]
• Celery Workers
• Android Builder
• Resource Customizer
Process Flow Representation
Main workflow:
Technical Details to Highlight
• Webpack bundling process
• Celery task distribution
• Centrifugo real-time messaging
• Redis data flow
• OAuth2 authentication flow
Remember to include version information for major components and mark potential scaling points, as this is a distributed system designed with scalability in mind.