new feature suggestion: local config file

[Ludovic Gasc]

Hi everybody,

After some discussions with some API-Hour community members, a feature seems to be missed:

Permits to have a second config file of main.yml that it could be read after main.yml but only override the content of main.yml, not replace everything like now.

The use case is when you add a new config option in your application in dev, you must remember to add the same option value in main.yml on your production.

Without this, your daemon won't start.

The idea is to keep your main.yml in your git repository, and put your modifications in a file named, for example, local.yml, not versioned in your Git via .gitignore.

I'm working on a "prototype", if you have any suggestion, I'm interested in.

Have a nice week-end.