Webpanel for configuration

[freaktechnik]

Make the configuration editable via web panel. This requires a few changes, as the current architecture assumes a static configuration.

However a web panel would allow for easier setup (authentication) and easy change of configuration values like schedule times for events etc.

Tasks

• Prepare configuration
  • Ensure configuration is read whenever possible instead of cached
  • Add infrastructure to dynamically add and remove instances of Boards (ideally the same as for Sources)
  • Add infrastructure to dynamically add and remove instances of Sources (ideally the same as for Boards)
  • Add an alternative config back-end (likely a database), designed in a way that would also allow state to be stored in it at a later point
• Add a web front-end for configuration
  • Simple multi-user management with privileges
  • Allow creating board instances and have simple key-value configuration of settings. Users should be able to be assigned privileges to individual boards.
  • Add integrated OAuth flows for GitHub and Twitter (which will require static configuration of those secrets again).
• Make this as easy as possible to deploy with docker (having a DB and a web front-end etc.) as possible. This should be optimized for the mesos workflow of PAAS.

Notes

Should not need to swap out API clients ever, since the instance should be removed on change of the authentication of any API client. Once the authentication is valid again, the board should be started again.

[freaktechnik]

There would also be completely new scenarios like renaming things on github (project, columns, labels).

[freaktechnik]

Feel free to split sub tasks of this into new issues if you plan to work on any of them. Note that sub-tasks should mostly be independent from each other, at least for the whole config preparation.