How tjcsl/othello-tourney works
Client-Side Layer
• Web Browser Interface
• Static Assets (CSS/JS/Images)
• WebSocket Connections for Real-time Gaming
Web Server Layer
• Django Application Server
• ASGI Server (for WebSocket support)
• URL Routing System
Authentication Layer
• Ion OAuth Integration
• Custom User Management System
Core Application Components
• Games Module
• Tournaments Module
• Authentication Module
• Error Handling Module
Background Processing
• Celery Worker
• Task Queue System
• Tournament Management Tasks
• Game Processing Tasks
Security Layer
• Sandboxing System (for running AI submissions)
• Code Validation
• Submission Management
Data Storage
• PostgreSQL Database
• Redis (for Celery and Channels)
• File Storage (for submissions)
Component Relationships
• How the Games module interfaces with the Moderator
• Tournament management flow
• Demonstrate authentication flow with Ion OAuth
• How Celery workers interact with the main application
Game Flow
• Client -> WebSocket -> Game Consumer -> Moderator -> Sandbox -> AI Submission
Tournament Flow
• Tournament Manager -> Celery Tasks -> Game Scheduler -> Game Execution -> Results Processing
Authentication Flow
• Client -> Django -> Ion OAuth -> User Management
Additional Notes:
• Annotations for critical components
• Scaling points (where the system can be horizontally scaled)
• Monitoring and logging points
• Security boundaries and sandboxed environments
Remember to include version information and any relevant deployment-specific configurations in a separate notes section.