Open lxe opened 9 years ago
@lxe
data center specific configuration was a first class requirement of a production quality config loader and will stay so.
Data center requirement is not something most people, or even "production" deployments will ever need. This requirement is tightly coupled with pre-existing assumptions about your environment, making zero-config very non-generic.
@lxe disagree. If you do not future proof your app you will fail.
An example of "datacenter" is staging vs prod, west vs east.
But it's an application/project specific feature, not a zero-config requirement. Zero-config should just load config, instead of managing/enforcing devops requirements.
An example of "datacenter" is staging vs prod, west vs east.
That's similar to what I'm suggesting... we can make environment-based loading generic and still satisfy datacenter requirements of projects that choose to adhere to it.
I don't think it should be a requirement either.
I don't think the 'dc' config should be a first-class citizen in this module, or a strict requirement.
Instead, we should be able to provide multiple paths, if you need to load up some host-specific config: