Rapid Router (codename: ocargo)
Code for Life projectA
- Rapid Router is a Code for Life project, aimed at teaching primary-school children programming concepts through a vehicle routing game. Ocado Technology's Code for Life initiative has been developed to inspire the next generation of computer scientists and to help teachers deliver the computing curriculum.
- This repository hosts the source code of the Rapid Router game.
- The other repos for Code For Life:
To use the app
Go to the official Code For Life website.
To run localy with Docker
To run the app locally
- Clone the repo:
https://github.com/ocadotechnology/rapid-router.git. Fork it first if you want to contribute, and work on a separate branch for your work.
Ubuntu / Linux Mint
sudo apt-get install git
sudo apt-get install python-dev python-pip
sudo pip install virtualenvwrapper
sudo apt-get install libxml2-dev libxslt1-dev zlib1g-dev gettext
sudo apt-get install ruby2.0
sudo gem install sass -v 3.3.4- tested to work with Ruby >1.9 and <2.3.6
Make and activate a virtualenv
e.g. the first time,
mkvirtualenv -a path/to/rapid-router rapid-router
NOTE: If you have trouble running these commands (e.g.
Command not found: workon), refer to this article, the top answer should help you resolve them. You may need to run:
export WORKON_HOME=~/Envs source /usr/local/bin/virtualenvwrapper.sh
brew install rbenv
brew install pyenv
brew install pyenv-virtualenv
.zshrcwith the following
eval "$(rbenv init -)"
eval "$(pyenv init -)"
eval "$(pyenv virtualenv-init -)"
Close and open terminal
Run the following commands
rbenv install 2.2.9
brew install zlib
brew install readline xz
pyenv install 2.7.14
Finall, go to the project root and create
.python-version, containing the versions you installed above.
Running the Portal
./runin your rapid-router directory - This will:
- install all of the dependencies using pip
- sync the database
- collect the static files
- run the server
Once you see
Quit the server with CONTROL-C, you can open the portal in your browser at
If you have problems seeing the portal on machines with different locale (e.g. Polish), check the terminal for errors mentioning
ValueError: unknown locale: UTF-8. If you see them, you need to have environment variables
LC_ALLboth set to
- Either export them in your
- or restart the portal with command
LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 ./run.
- Either export them in your
- For localisation admins:
./run --with-translation-toolsin your rapid-router dir to include the translation/localisation libraries
- You will need your crowdin api key locally in the
CROWDIN_API_KEYenvironment variable, e.g.
export CROWDIN_API_KEY=<key>. This can be obtained from the settings page
- Set your
lol-usto enable in-context localisation
Guidelines Please read the contributing guidelines first, thank you.
Found a problem? Please check whether it has already been reported in our issue tracker first! If not,
add it. Please make sure that you give us a suitable level of detail about the symptoms and how to
reproduce it. Please label it as a "bug".
One word of caution: please do not add any issues related to security. Evil hackers are everywhere nowadays... If you do find a security issue, let us know using our contact form.
Want to suggest a feature? Please check whether it has already been added to our issue tracker first! if not, add it. Please make sure that you give us a suitable level of detail about the feature. Please label it as a "suggestion". Please note that we may not act upon all suggestions, if they are not in line with the direction we want to take the project, or if we don't have the development resources to get it done.
Want to help develop? You can contact us using this contact form and we'll get in touch as soon as possible. To know what's going on, check out the issue tracker. The issues with the 'ready for pickup' label are tasks we think are ready to be picked up. Once you have chosen an issue, make sure you assign it to yourself so others don't also pick it up. Develop it on your fork of the project. Please ensure all files have the license at the top (see another source file for an example). Once you are happy that it works, and have written tests for it, submit a pull request. We'll then look to review the changes. If it looks good, we'll merge it. If we find issues with it, we'll let you know and hopefully we can work with you to improve it and get it re-submitted. If it is a change that we just don't want, we'll reject it.