How ntueelightdance/lightdance-editor works
Main Components
• Clients
– Web Frontend (served by editor-server)
– Blender Add-on (editor-blender)
– Command-Center App (Python CLI/GUI)
• Services
– editor-server (GraphQL + REST API, port 4000)
– file-server (static assets, port 8081)
– controller-server (RPC/WebSocket to RPis & control panels, port 8082)
• Data Stores
– MySQL (Prisma ORM)
– Redis (pub/sub for subscriptions & caching)
• External/Utility
– Docker Compose for dev/prod
– initDB & post-processing scripts (utils/)
– NTP sync, backup scripts
Relationships & Flows
• Web Frontend ⇄ editor-server via GraphQL HTTP
• Blender Add-on ⇄ editor-server via GraphQL/subscriptions
• editor-server ⇄ file-server for 3D/model assets
• editor-server ⇄ MySQL (Prisma) & Redis
• Controller-server ⇄ RPis & Control Panels via WebSocket
• Command-Center ⇄ controller-server via HTTP API or WebSocket
• initDB scripts write initial data into MySQL
Architectural Patterns
• Micro-services: three independent HTTP/WebSocket services
• CQRS & Subscriptions: editor-server uses GraphQL queries, mutations, subscriptions
• Asset Server: file-server serves heavy binary/model files separately
• Client-side extension: Blender plug-in communicates same APIs as web
Technologies & Frameworks
• Node.js/TypeScript (controller-server, file-server via static serve)
• Rust + Prisma (editor-server)
• Python (command-center, editor-blender)
• GraphQL (editor-server) + WebSocket
• Docker Compose for orchestration