Project management #2941
Replies: 2 comments 2 replies
-
Monorepos have many advantages over split repos. What specific advantage do you see with splitting? |
Beta Was this translation helpful? Give feedback.
-
This is a never ending conversation and there is no right answer. I think it depends a lot on context, and for Immich I think a single repository makes the most sense. Immich is a small team of volunteers and the overhead of managing multiple repositories would be a huge negative impact on productivity. Less active components will also be more likely to rot, as we have already observed with the cli. If we can barely manage two repositories, I struggle to see how we could manage 8 or more repositories. I currently do not see much pain from using a monorepo and really only see positives. It also makes cross-component changes (i.e web and server) really easy. The amount of effort required to split Immich into multiple repositories just doesn't make sense to me, and I think it would kill velocity with increased complexity. We're actively looking to merge more things into this repository (again, the cli) because it will be much easier to manage and distribute. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I noticed that Immich currently uses just one repo as a monolithic repo.
I think that splitting the project in different repositories would make easier for third-parties to help developing Immich.
Is there any specific reason why the backend is in the same repo as the mobile application or it is just "always been like that"?
Beta Was this translation helpful? Give feedback.
All reactions