A competitive coding platform where players solve programming problems against the clock, get instant feedback from an automated test runner, and climb a live leaderboard.
beta-code runs timed coding competitions. An admin configures a start and end time, creates tasks with hidden test cases, and players race to solve as many as possible for points. Submissions are compiled and run against test cases automatically, with results (accepted, wrong answer, or compile error) shown immediately.
New players create an account, existing players log in. Both forms are on the same card, toggled by tab.
| Login | Sign Up |
|---|---|
 |
 |
Once logged in, the navbar shows the current username and a logout option.
The homepage shows a live countdown to the competition's configured start time. Once the countdown hits zero, the page updates automatically and a Go to Tasks button appears.
Once the competition is live, players see the full task list with difficulty and point values, along with a running count of how many they've completed.
Each task has a description, starter code in an in-browser editor, and a Run button that compiles and executes the code against the task's test cases.
Results are shown right below the editor:
-
Wrong Answer — shows the input, expected output, and actual output for every visible (non-hidden) test, plus a pass/fail summary line for the hidden grading test (its contents stay secret, only the verdict is shown).
-
Compile Error — shows the raw compiler output so players can debug.
-
Accepted — the task is marked complete and points are awarded.
Completed tasks are highlighted in the task list with a checkmark, so players can see at a glance what's left.
The leaderboard shows a countdown to the competition's end time, a live score-progress chart per player, and a ranked table of players by points and tasks completed. (Work in progress)
Admins get a separate panel with four tabs for managing the competition.
Players — view all registered players, their points and completed tasks, manually assign tasks, and delete accounts.
Tasks — create new tasks with a name, description, starter code, point value, type, and difficulty, and manage existing ones.
Tests — attach sample or hidden test cases (stdin input + expected output) to any task, optionally with a supporting data file.
Existing tests for a task can be reviewed and edited from the same tab:
Settings — set the competition's start and end time (the leaderboard freezes 15 minutes before the end), or start the competition immediately.
- Docker installed and running
- Node.js and npm installed
- Redis (via Docker)
Run this in root to get all the packages:
npm run install:all.env files hold local secrets and aren't committed to git. Copy the template and fill it in (a RUNNER_SECRET is required — the frontend refuses to serve test data without one):
cp frontend/.env.example frontend/.envGenerate a RUNNER_SECRET value with:
node -e "console.log(require('crypto').randomBytes(32).toString('hex'))"Paste it into frontend/.env, and use the same value in the RUNNER_SECRET= env var in the root package.json start/build scripts (the runner process reads it from there, not from a .env file).
Run this in root:
npm startTo stop the services, press Ctrl+C in the terminal window, then run:
npm run stop| Username | Password |
|---|---|
admin |
admin123 |