How tunghoang/procon-team-manager works
Project type and purpose
• This is a full-stack web application (“Procon Manager”) that provides a static SPA frontend (in build/) and a Node.js/Express backend (in src/) exposing RESTful APIs, backed by a relational database and a background job queue.
File structure
• Top-level
• build/ ← compiled frontend assets (HTML/CSS/JS/images)
• src/ ← backend source code
• *.sql ← database schemas/data for contests
• package.json ← Node.js dependencies & scripts
• src/
• routes/ ← Express route definitions (REST endpoints)
• controllers/ ← business logic for each resource (tournament, round, match, question, answer, team)
• models/ ← ORM models (dbInstance.js + table definitions)
• middleware/ ← authentication & other request filters
• lib/ ← shared utilities (encryption, common helpers, dynamic controller loader)
• jobqueue.js ← background‐job producer/consumer logic
• docs.js + swagger.json ← API documentation setup
README
• “npm/yarn dev” spins up the dev server
• “/docs” serves API documentation (Swagger UI)