How tjcsl/tin works
Main System Components
a) Web Application Layer (Django)
• Core application with multiple Django apps (assignments, courses, submissions, users, venvs)
• Authentication system (OAuth support)
• Admin interface
• Template-based frontend
b) Task Processing Layer
• Celery worker system
• RabbitMQ message broker
• Task queues for grading submissions
c) Database Layer
• PostgreSQL (primary database)
• SQLite (secondary database)
d) Sandboxing System
• Container management for running student code
• Isolation mechanisms
• Network access controls
Component Relationships
[Web Browsers] ←→ [Django Web Server]
• ↑↓
• [Database]
• ↑↓
[RabbitMQ] ←→ [Celery Workers] ←→ [Container Runtime]
Detailed Component Breakdown
a) Django Apps (show as interconnected modules):
• Assignments (managing assignments and grading criteria)
• Submissions (handling student code submissions)
• Courses (course management and organization)
• Users (user management and permissions)
• VEnvs (virtual environment management)
b) Security Layer:
• Sandboxing mechanism
• Container isolation
• Network access controls
• Permission management
Data Flow Indicators
Key flows:
Student submission path
Browser → Django → Database → Message Queue → Celery → Container → Results
Teacher grading path
Browser → Django → Assignment Configuration → Database
Authentication flow
Browser → OAuth → Django → User Session
Technical Details
Annotations for:
• Python/Django backend
• Celery task queue
• PostgreSQL/SQLite databases
• Container runtime
• Static file handling
• Template rendering system