Hi!

As we have seeing with many Unix packages sometimes configuration files grow complex, long and difficult to handle.

Many projects out there support the following pattern: one big config file, or one directory with many configuration fragments.

For example, one can configure the popular APT tool by editing apt.conf, or by adding a configuration fragment as a file into the directory apt.conf.d

I think this pattern is very good on multiple scenarios. When files grow big and also when configuration is automated with tools like puppet, in which a configured role might handle only some configuration aspects of a package.

so, it would be great to be able to do something like:

default.json
production.d/
production.d/external-proxy.json
production.d/database.json
development.d/database.json

Or similar...
I would like to suggest to add this or similar functionality to the conf roadmap.