RaceDB: Support for public websites
Post date: Apr 18, 2017 2:31:22 PM
RaceDB now includes a number of new features to help with deploying it on a public server.
First and foremost, it is now possible to change the passwords of the "super" and "reg" roles. This can be done from a command line command:
python manage.py set_password username password
where username is "super" or "reg", and the password is the new password. This allows you to change the default passwords so you can control who has access to your RaceDB instances.
Another security feature has been added relating to cloud upload/download.
First some background. For a number of months, RaceDB has had the feature to upload and download an entire Competition to another instance of RaceDB. This also synchronizes all athlete information.
The purpose of this is so that you can maintain a cloud instance of RaceDB running on a public server, then run a local instance of RaceDB at a race site. After you have all the local results from CrossMgr, and when you have a good internet connection, you can publish from the local instance to the cloud instance of RaceDB (likely running in "Hub" mode).
If you are unfamiliar with Hub mode, take a look here. RaceDB Hub mode is a fully linked set of results for all races. It also computes Series points based on the results. Each race result also has access to an "athlete dashboard" which allows a detailed comparison, lap-by-lap, with any other competitor in the race.
In your RaceDB folder is a new file called RaceDBSecret.txt. With a text editor, enter a secret key in this file. Now, only RaceDB instances with exactly the same RaceDBSecret.txt file will be able to upload/download to each other.
This allows you to prevent unauthorized changes to your cloud RaceDB.
Comments? Suggestions? Let me know!