Use configuration files instead of value definitions in class.

[lastland]

Configuration files may be a more intuitive way to make configurations for users. In this way the configurations can be changed even after the program has been compiled, and does not require a re-compilation. Having configurations in configuration files also allow the program to read settings such as db location, during compile time or even sbt loading time, which enables doing something requiring these settings in a macro or programs under sbt project/ directory.

[cvogt]

I actually think that putting configuration into a separate sub-project as scala object with vals is the right way to do configuration, but indeed nobody is doing it this way and it may be unfamiliar and less well supported so lead to a more complicated setup. In that sense LGTM. Merge it :)