VPS

Tools

PuTTY is a great tool for easily connecting to SSH sessions. Highly recommend.

Connecting to the VPS

You should get these from someone who probably has them. For some reason it's against standard security practice to put the SSH keys on here, so I'll leave that up to you to figure out.

Username is ubuntu

Django vs Node.js sections

This project is a merger of two different applications. One uses Django, while the other uses Node.js.

Node.js	Django
Stats Manage	Stats Teams
Stats Graph	Stats Matches
...	Scouting Form
...	Set Scout
...	Schedule
...	Help
...	Administration
...	Literally everything else

Making changes to the Django site

The main important folder is Scout-Janssen. To get changes, do

cd Scout-Janssen/
sudo git pull

Note that some changes will not take effect until the service is restarted.
This is almost every change besides for static and template changes. The easiest way to do this is to reboot with

sudo reboot

Static Changes

Changing static files (css, js, images) require an additional step. Or a few steps, actually. From the home directory ~,

sudo -s
source sjenv/bin/activate
cd ScoutJanssen/scoutjanssen/scoutingtool
python manage.py collectstatic

More on using manage.py

The reason we switch to the root user in the above step is that this is badly configured. But it's fine and acceptable and no one is going to change it because it's fine and acceptable and if we do it will break the database again and it's fine and acceptable.
Similarly, we may have to use the root user to do other commands that modify the file structure. To do that, we have to switch to to the root user with

sudo -s

To run any python command, however, we have to use the source command on sjenv/bin/activate. This puts us in a python virtual environment which can use the right modules, the right version of python, and the right environmental variables. You have to use this whenever you install a python module or run a python file in this project.

source sjenv/bin/activate

Running local versions of the website

Our testing environment is our production environment. Which is bad. But be my guest if you want to fix that.
You can try to set up this project on a local machine, and I wish you the best of luck.
If you're attempting to do that, you should know that the way we're connecting the server to Nginx is through WSGI, and you'll have to remove the parts in the code which reference it on your local machine and make sure they're still included in production.
Above all else, keeping a stable version of the website going during competition is priority!

Making changes to the Node.js site

Carter send help

Database

WSGI

Services

Statistics Service

Node Service