3 ms·
The article links to a site with this definition: > A monorepo is a single repository containing multiple distinct projects, with well-defined relationships.
by boxed 1y ago
The article links to a site with this definition:
> A monorepo is a single repository containing multiple distinct projects, with well-defined relationships.
It would be better if there were terms that delineated "one repo for the company" from "one repo per project" from "many repos for a single project".
- bluGill 1y agoIdealy the term would indicate code and team size. Many commenting are working on tiny projects where they don't even see the problems that cause one to think of this debate
- wocram 1y agoI think most monorepo advocates are actually anti "one repo per project" at heart. That's the real anti-pattern imo.
- boxed 1y agoI don't get it. That's the only pattern that makes any sense imo. If you get problems because two or more projects needs to be updated simultaneously because of DRY or whatever, I would argue that you actually have ONE project and you're just fooling yourself. Hmm.. actually, I guess that's what you're saying? When I said "project" above, I meant something like "product" or "system".