So you run into the same issues as the scenario above using an umbrella app? You’d have a separate instance of application C running for A and B?
anthonator
michalmuskala
AFAIK in_umbrella: true is a shorthand for path: "../<dep_name>", so I wouldn’t consider it a big difference.
0
hubertlepicki
Biggest difference lies in how the umbrella apps are generated, and in fact their configs. So in umbrella project all the relevant config files from all the apps will be loaded, i.e. config is shared by default.
When you build the project from multiple independent apps, you can either do that, or not. For example, I can have separate config/test.exs for each app, so I can test those in isolation (and even in parallel), mock some stuff in ui app and hit the database in db app (or other way around, as I please).
So the biggest advantage of not having umbrella project is that you don’t share the same config across all apps and it’s up to you how you configure it all.
5
michalmuskala
Yup, config handling is different because of how it is generated. It’s nothing inherent, though, if you look at the config files (and the config_path: "../../config" setting in mix.exs), you’ll see you can easily change how it works to have a per-app config.
8