This is the "buggy editor" component of the Foundation Year Computer Science project at RHUL.
This is the skeleton of an application for editing a racing buggy.
It runs as a webserver so you can edit the configuration of a buggy in your browser. The editor can then generate the data, in JSON format, that you need in order to enter races on the race server.
The application is written in Python3 using the Flask microframework.
It's also written in a way which you can and should fix! You should be able to get it up and running (with SQLite) without needing to change the code... but from that point on you'll need to change pretty much everything to make it better (including switching away from SQLite, perhaps?).
GitHub repo: RHUL-CS-Projects/CS1999-buggy-race-editor
We recommend you clone/download this repo onto your own machine where you can begin developing on it: see the installation and set up instructions below (of course we also talk you through this at the start of the project).
But if you have problems with that, or you don't have access to your own machine, you can work on it on https://repl.it.
- fork this repo into your own GitHub account
- log into repl.it
- click on "+ new repl"
- click on "Import from GitHub"
- enter the URL of your forked repo
- click Import from GitHub
- when it's finished, click Run
You've got a file browser, editor, website pane and shell window all in your
browser. Because you forked from your copy of the repo, you can git push
any changes you make back there.
Getting the editor running on your own machine differs depending on which operating system you're using. The principles are the same, but the way to execute them is slightly different.
The recommended way to run this app this on your own machine is to first install it:
- install the software (clone this repo)
- create a virtual evironment
- install the dependencies (e.g., Flask) in that environment
Then, to run the application:
- activate the virtual environment
- run the app
- kill the app with Ctl-C
- deactivate the virutal environment
This varies a little depending on which platform you are using.
You must have these two things installed before you can start:
If they are not already installed on your machine, see the downloads/installation instructions on their respevtive websites.
When you first install the buggy editor webserver you need to install some Python modules. Instead of installing them on your whole machine (which might be a problem if other applications need different versions of the same libraries) it's best to create a virtual environment just for this project, and work inside that.
On Windows you can follow these instructions in the PowerShell. Alternatively if you use the Windows Subsystem for Linux (WSL) you can follow the instructions as Linux.
For Mac or Unix-like systems, open a Terminl window.
To create the virtual environment, first cd to the directory which contains
the application files (you might have use git clone to create it). Then do:
python3 -m venv venv
This creates a directory, called venv, where Python will keep the library
files this virtual environment uses.
Python has created a file inside that directory that you can execute at any time to activate the virtual environment. Once you've activated it, all subsequent python commands operate within the scope of this environment (instead of your whole machine).
Activate the virtual environment. On Windows, do:
.\venv\Scripts\activate
On Linux or Mac:
source venv/bin/activate
Next, install the libraries the app needs. Because you activated venv, they
will be installed in this virtual environment:
pip install -r requirements.txt
Finally, set up the database:
python3 init_db
This creates a SQLite database in a file called database.db.
There's no configuration file to edit. You're ready to go!
If you're not already in the project's directory, cd into it.
Then, if you haven't done so already, activate the virtual environment:
Activate the virtual environment. On Windows, do:
.\venv\Scripts\activate
On Linux or Mac:
source venv/bin/activate
Set the environment variable to development. On Windows do:
$env:FLASK_ENV = 'development'
On Linux or Mac:
export FLASK_ENV=development
Now you can run the application:
python3 app.py
The webserver is running on port 5000 (that's the default for Flask apps). If you make a request for a web page, it will reply with one!
Go to http://localhost:5000 in your web browser.
You haven't specified which file you want, so you'll get the / route, which
(you can see this by looking in app.py) invokes the index.html template.
You can see the webserver's activity in the terminal, and the result of its action in the browser.
In the terminal where the webserver is running, press Control-C. This interrupts the server and halts the execution of the program.
If you've finished, you can deactivate the virtual environment:
deactivate
You're done!
RHUL CS1999... that's a course number, not a year ;-)