Summary:
Allow the run-records database filename to be set in the server configuration so a separate development database can be used without touching production run history.
Description:
Testing the completed runs screen or trialling new run configurations required either risking pollution of the live run history or manually moving database files. There was no way to point the plugin at a separate database for development or QA purposes. The feature needed to let server operators specify a different database filename in the configuration file, have that database created and fully migrated on startup if it did not exist, and revert to the production database with a one-line config change. The default behaviour needed to remain unchanged for servers that did not set the option.
Estimated Ideal Time: 1 hour
Summary:
Allow the run-records database filename to be set in the server configuration so a separate development database can be used without touching production run history.
Description:
Testing the completed runs screen or trialling new run configurations required either risking pollution of the live run history or manually moving database files. There was no way to point the plugin at a separate database for development or QA purposes. The feature needed to let server operators specify a different database filename in the configuration file, have that database created and fully migrated on startup if it did not exist, and revert to the production database with a one-line config change. The default behaviour needed to remain unchanged for servers that did not set the option.
Estimated Ideal Time: 1 hour