Define how configuration will work

[txels]

Deploystream should be designed as a system that supports site-wide settings, plus user-specific settings.

And eventually, if this is going to be a shared hosted solution, we need to support team/organisation settings as well. And having settings in files is no longer an option, IMHO, we need to be able to store settings in the server and access and change via an API like the rest of the application.

I think we have to address this issue early on, meaning that at least some form of user authentication (e.g. Oauth via github account) and personal settings must be supported since the early iterations.