We can move this to consul for easy updates too.

Would this also be used to update the version information in the default_config.py file for the api releases endpoint (if and when the PR is merged)?

EDIT: Please disregard my note. I just went through the code and see that the two are separate parts of the same configuration file. I should have looked more closely originally. Sorry about that.

@samj1912, with this being developed in parallel with PR-119 I think that the current release version tag will now be entered in two places: once for the api and once for this easy updating. Ideally it should probably only be entered in one place and copied to the other variable. This would avoid the situation where the website and the api display different versions because the information was only updated in one place.