Public | Automated Build

Last pushed: 7 months ago
Short Description
Platform used for the qualification round of the beOI contest
Full Description

beOI Qualification Platform

This platform is a fork from the French Beaver Contest.

Developer deployment (local)

You can use the local Dockerfile and docker-compose file to run the platform locally to setup the platform together with a database. In short, you should be able to run the project via:

docker-compose build
docker-compose up

Then the service should run on your Docker port 80.

  • If you cannot connect, you might need to change the site's IP address configuration to whichever address docker assigns to your VM: amend config/config_dev.php and replace the IP addresses. Docker-machine default IP is often
  • To avoid mounting errors in Docker for Windows, the repo should be on the same drive as the Docker installation (e.g. C:). Also remove the volumes section in file docker-compose.yml. Run the commands above after navigating to the repository directory in Docker Quickstart Terminal.

Production deployment

The config/aws.cloudformation.yml file defines the AWS CloudFormation containing everything requires to run the contest system on Amazon Web Services. It includes:

  • The DynamoDB table (for sessions, teams and team questions)
  • The S3 bucket for logs and static files
  • The CloudFront (CDN) to serve static files
  • The RDS MySQL database
  • SSL Certificate for EB
  • The Elastic Beanstalk (EB) configuration

The stack uses instance roles and environment variable passing not to require any password passing, appropriate credentials are available on the server with the defined role permissions.

For EB, only the stored configuration will be updated, not the running one. So once the stack for EB has been updated (risk-free), you need to update the running environnement to run with this config.

At creation, the SSL certificate create requires to validate the domain ownership via a confirmation e-mail. The stack creation will not complete as long as this confirmation has not been done.

Database initialisation

At first run, the database has to be initialized from migration. It can be done by visiting dbv/index.php using as user and password the database credentials.

In development, the database can be cleaned by removing the db docker (docker-compose rm db). The sample database can be loaded using mysql -h db -u dbuser --password=password -D beaver_contest < sampleDatabase/database_content.sql.

Original instructions


You need:

You also need a web server with PHP (>= 5.5) and a MySQL database.


Clone the repository:

git clone
cd bebras-platform
git submodule update --recursive --init

Copy config_local_template.php into config_local.php, and set the parameters for URLs and database.

Visit dbv/index.php with your web browser, login and passwords are those of the database.

Get composer dependencies:

composer install

Make the directories logs/ and contestInterface/contests/ writable by PHP.

Get Bower dependencies: run bower install in both contestInterface and teacherInterface.


The database can optionally contain triggers writing in the different *_history tables. To install them, run php commonFramework/modelsManager/triggers.php. Note that before going into production, you must remove by hand the triggers in team, group and question.


If you want to test the platform, run sampleDatabase/database_content.sql in your database.

For translation and country-specific features, please refer to the documentation.

For installation on AWS, see


git pull
git submodule update --recursive
composer install
cd contestInterface && bower update && cd ..
cd teacherInterface && bower update && cd ..

Initial configuration

Create an admin user: go to /teacherInterface/, register
through the link “Register!”. For the first user, you need to
validate it manually through the database. A record should have been
created in the “user” table, and you need to set the fields
“validated” and “isAdmin” to 1. You can then log in on the
/teacherInterface/index.php page.

Generate contests: contests need to be “generated”, which means compiling all of the
questions into a single HTML file, a CSS file, a JS file and a PHP
file. You do that as an administrator in the “Contest” tab by selecting a
contest in the first grid, and clicking on “Regenerate selected contest”.
Make sure PHP has read/write access to the contests folder,
where it will create a sub-folder for each contest that you
generate. The interface doesn't say anything if there is an error, so
you have to check that the folder has been created.

Once contests have been generated, you can try them as a contestant:
go to contestInterface/index_en.html in the root folder. It should look exactly the same
and you can click on any contest that has been generated.

Note that if it were a production server, you would want to put an
.htaccess file or equivalent in the questions folder, otherwise people
will be able to access questions before the contest. You will need to
input the corresponding login/password if you want to preview
questions from the admin interface.

Teachers use a reduced version of the admin interface, so you might
want to create a different user, that is not an admin to see how it
looks. For that, register a new user through the interface, and set
“validated” to 1 from the interface of the admin user. Teachers can
create groups, and get a password that students input to participate
in the corresponding contest (this is explained in detail in the
“Explanations” tab). When a contestant participates through a group,
there are two extra steps compared to the public contest: he/she is
asked for the number of students doing the contest as a team (1 or 2),
then each student is prompted for her firstname, lastname and gender.
Other than that, everything works the same way as public contests.

Common problems

  • Something doesn't load. Check out the web console to know why.
    If a contest doesn't generate, verify PHP can write into the contestInterface/contests/ folder.
  • I get a 404 error. Check your URLs. Be sure not to mix server name synonyms (like and localhost)
    as some web browsers block third party calls. Verify your contest has been generated.


  • Prepare gulp files for contestInterface and teacherInterface to compile all needed dependencies into one big uglified JS (see this example) and document it into the installation.
  • Tests!
  • Make task directory configurable (now it's certainly hardcoded as bebras-tasks).
  • Tracking/ has unmet external dependencies (should probably link to external CDNs).
Docker Pull Command
Source Repository

Comments (0)