How cms-dev/cms works
CMS is a distributed programming-contest management system. Contestants use the contest web app to register, submit solutions, and view contest information; administrators manage contest data and operations. Submissions are evaluated by language/task-specific grading components, with results and scores coordinated by services and persisted in the database. The README also describes configurable task and scoring types. The graph emphasizes documented entry points and service connections; some implementation links remain uncertain because many source files were not sampled.
Main entry points: EvaluationService.py Evaluation Service · contest/server.py Contest Server · handlers Contest Handlers · admin/server.py Admin Server
Components 20
Contest Web
- Contest Server
cms/server/contest/server.py - Contest Handlers
cms/server/contest/handlers - Submission Handler
cms/server/contest/handlers/tasksubmission.py - Admin Server
cms/server/admin/server.py - Admin Handlers
cms/server/admin/handlers - Phase Management
cms/server/contest/phase_management.py - Ranking Web App
cmsranking/RankingWebServer.py
Grading
- Grading Job
cms/grading/Job.py - Language Manager
cms/grading/languagemanager.py - Task Types
cms/grading/tasktypes - Grading Steps
cms/grading/steps - Scoring
cms/grading/scoring.py
Distributed Services
- Evaluation Service
cms/service/EvaluationService.py - Scoring Service
cms/service/ScoringService.py - Proxy Service
cms/service/ProxyService.py - Service RPC
cms/io/rpc.py
Contest Data
- Contest Database
cms/db - File Cache
cms/db/filecacher.py
Other components
- Contestant
- Administrator
Connections 18
- Contestant → Contest Server: uses
- Administrator → Admin Server: uses
- Contest Server → Contest Handlers: routes
cms/server/contest/server.py - Contest Server → Evaluation Service: connects
cms/server/contest/server.py - Contest Server → Scoring Service: connects
cms/server/contest/server.py - Contest Server → Proxy Service: connects
cms/server/contest/server.py - Admin Server → Evaluation Service: connects
cms/server/admin/server.py - Admin Server → Scoring Service: connects
cms/server/admin/server.py - Submission Handler → Language Manager: uses
cms/server/contest/handlers/tasksubmission.py - Submission Handler → Scoring: uses
cms/server/contest/handlers/tasksubmission.py - Evaluation Service → Scoring Service: connects
cms/service/EvaluationService.py - Evaluation Service → Contest Database: writes results
cms/service/EvaluationService.py - Evaluation Service → Grading Job: uses
cms/service/EvaluationService.py - Grading Job → Language Manager: uses
cms/grading/Job.py - Grading Job → Contest Database: uses
cms/grading/Job.py - Evaluation Service → Service RPC: uses
cms/service/EvaluationService.py - Contest Handlers → Phase Management: uses
cms/server/contest/handlers/contest.py - Contest Handlers → Contest Database: uses
cms/server/contest/handlers/main.py