thenerd247 / ariaracer Goto Github PK

A good idea may be to spin up a container that pulls from the user's git repo to build and run the code. That is each user will have his or her own docker container that will be rebuilt each time a user uploads his/her code. Then to run a race we simply boot up the necessary docer containers.

• Remove test Aria project
• add .gitignore for build directory

Add race times for the lanes that are racing.

• start the clocks when start is pressed.
• stop the clocks when the lane is stopped.

Might as well add the stats to the racer's build (show fastest race time for each build).

• AcidState
• Command protocols

The Mongo layer needs to be created. We'll need documents for

• Uname
• Passwd
• Racer Id
• Racer source code
• Tournaments
• Match info
  • Racers and times
  • Winner
  • Date

The backend layer of the webserver needs to be created.

• Move base types created in Pages.Types to Data.Racer
• Create data operations (CRUD tournaments, races, etc).

The criterion for uploading a form is as follows:

• Build name is required
• the upload file must be a cpp file.

If a script fails to run:

• grab the cooresponding script log
• return a script failed page with log information.

Create the race manager front and back ends:

Front end

Front end will exist on the admin/home page

• 1 start button
• 2 racer stop buttons
• 1 all stop button
• return to race manager button

Backend

Backend will have the following scripts:

• Start a race and save the executable PIDs to a file
• A stop script that takes a list of lanes to stop. The corresponding PID is then terminated.

Have the upload/select form build the code.

Each process continues if the build succeeds (code is committed).
Otherwise, the repo is reset to the previous branch (handled by the build script) and an error page is returned with:

1. The build log so the user can fix compile-time errors
2. A link to their home page.
3. A message telling the user to fix their code and try the upload again.