Review the scope of the configuration file "secrets.yml"

The following discussion from !1 (merged) should be addressed:

• @clemenci started a discussion:

  We should review the scope of the configuration file.

  I would prefer something more generic than just secrets, definitely with the possibility of overlaying configuration files (so that we can have generic configurations in a public place, and secrets managed independently).