Thanks Grzegorz for your answer.
The only things that applications have common are:
- Users (user models), centralized authorization
- Some components (or component slots) from app A (for example) can
be used in app B or C.
And another question -- is it unneffective to store all the data in
It's not matter of git, but rather the matter of your development
strategy.
If your apps are supposed to work within one project, then one repo is
what you need, if these apps are in fact three different projects,
then second idea is right.
You can always have different branches for each
