How bubblehouse/django-moo works
Main Components
a) Client Layer:
• SSH Client Interface (Port 8022)
• Web Admin Interface (Django Admin)
b) Application Services:
• Web Server (Nginx)
• Application Server (uWSGI)
• Shell Server (SSH Service)
• Task Queue (Celery, indicated by celery.py)
c) Core Components:
• Authentication System
• Object System
• Verb System
• Parser
• Permission System
• Property System
• Task System
d) Data Layer:
• Database (Django ORM)
Key Architectural Elements
[Client Layer]
[Web/Network Layer]
[Application Layer]
[Core Systems Layer]
[Data Layer]
Important Relationships
• How the SSH and Web clients connect through their respective servers
• Relationship between core components:
• Objects → Properties
• Objects → Verbs
• Verbs → Parser
• All components → Permissions
• Task queue workflow for async operations
Implementation Details
• Django's MVT (Model-View-Template) architecture
• Celery task queue integration
• Authentication flow
• Command parsing pipeline
• Object inheritance system
Deployment Components
Docker containers (as shown in docker-compose.yml):
• Webapp container
• Shell container
• Nginx container
• Database container
• Celery worker container
For this specific project, focus on showing how traditional Django components integrate with MOO-specific features like the verb system and object hierarchy, as these are what make this project unique from a standard Django application.
Remember to include the async capabilities of the system, as indicated by the presence of Celery and async verb handlers in the codebase.