There are two aspects that have been mixed. Env-driven and (compiletime | runtime)-driven file naming.
It appears we move toward the the latter. So in the end we should only have config/compiletime.ex(s?) and config/runtime.exs.
IMHO, Additional *_dev | *_test | *_prod is nice in theory. In practice it’s confusing rather than nicely managed separately.
Finally, with (compiletime | runtime)-driven file naming. Those files are going to be similar to Ruby’s Gemfile where shared config is on the top, then env based groups on the bottom. Though configs can be a lot in a single file, but again IMO, huge single file is pretty much good (same as we’re good with a module has full of documents hundreds of lines).
Note, however, some configuration files, such as
config/runtime.exsdoes not support imports, as they are meant to be copied across systems.
