That won’t work. config/config.exs and config/runtime.exs (and the deprecated config/releases.exs) are the only files mix knows about and those names are hardcoded. All other files in the config folder are convention, optional and need to be included explicitly by code from config/config.exs. So it really only is a base config if you make it that.
LostKobrakai
0
taro
I’m confused. It seems it’s working with
defmodule Feder.Mix do
use Mix.Project
def project do
[
...
config_path: "config/base.exs",
...
]
end
...
end
How can I tell apart if it’s not working? I see no sign.
0
LostKobrakai
Oh, didn’t know there were actually configurable (especially given there’s not just one file).
1
taro
UPDATE
What I was trying to do turns out to be called “Feature Slicing”, or “Vertical Slice Architecture”. From my short research, it seems
- Great for Agile/Scrum, some say it’s the only way.
- Suitable for small teams with distinctive roles, as opposed to well-orchestrated large group of developers.
https://gearset.com/images/blog/shipping-new-features-in-small-vertical-slices/vertical-slicing.png
1