Use literate config management

[blahah]

Ideally in general, and especially for projects with lots of contributors or where multiple teams might be responsible over time, sensitive information such as API keys, database configurations, etc, should be well documented and easy to control the permissions of.

This is a problem that is currently not well solved in general, and we are using a reasonable first approach given the scope of the project. We could make transitions between teams much easier by using a literate system, like (@mozilla/node-convict)[https://github.com/mozilla/node-convict]. Not urgent but will save costly developer time later.