> You can set up a generic config with default values for everything, and then have more specific configs that override the defaults. I was going to say the sa

> You can set up a generic config with default values for everything, and then have more specific configs that override the defaults. I was going to say the same thing - this pattern of having an "override" file in add to defaults, is something I've seen in multiple systems and liked. For example, it's used for JSON configuration in .NET, and with Docker Compose's YAML service configuration files.