Description
Config Madness
This is a mad idea, but i think its possible.. so lets go with a new concept...
of "revel integrated" configuration..
Though a journey of code, and config files in
- ini
- conf
- json js
- yaml yml
- txt
how I want to use ma djingo/2 interface and the git repos in that user accounts, and php.ini here and a json there...
The only thing I think, we all dream of is that we have to "config" somehow..
this is the config of the scenario.. even config machine to machine or somewhere else..and certainly sharing configs is a pin in the but...
I dont want to tap in the config, and if on e changes then the others..
So this means we need to somehow use revel to be a configuration and a service, and also a config that is reloadable..
Dreams
myxxx.config.conf
revel runconfig /home/me/my-silly.ini
or
revel runconfig /home/me/mobile.json
[well.Hello.There]
[db_engines]
require_refs conf/db
[db]
import_conf * /~/config/