chaoss
Create augur config file
- On startup take the file config and update the database with it
- On shutdown take the database config and update the file config
- All config changes made in tasks or gunicorn processes need to be made to the database
- All config reads need to be from the config file
Why are we storing config in the database? - that seems like it would have a major impact on horizontal scaling (and therefore #1389)
Why are we storing config in the database? - that seems like it would have a major impact on horizontal scaling (and therefore #1389
Because @sgoggins thought that was better than a file at one time ... and now recognizes that it is not it should be a file.
also it seems like the CLI that is described here was added in https://github.com/chaoss/augur/commit/d02e356b6e3613a89e2942c7a34094a61b091949 (pr #1917). so at least theres a chance we might already have a starting point for code that we can use as an export tool to help migrate people to a file based config system
This is important because the default config is currently defined in the source code, which means it is required to rebuild the docker image if you want to update the config