#monorepo — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #monorepo, aggregated by home.social.
-
#Dropbox cut its backend monorepo from 87GB → 20GB.📉
In collaboration with #GitHub, they fixed a massive bottleneck by optimizing Git delta compression.
The impact:
• Reduced clone times
• Improved CI performance
• Boosted developer velocityLearn more 👉 https://bit.ly/3R9pSfZ
-
#Dropbox cut its backend monorepo from 87GB → 20GB.📉
In collaboration with #GitHub, they fixed a massive bottleneck by optimizing Git delta compression.
The impact:
• Reduced clone times
• Improved CI performance
• Boosted developer velocityLearn more 👉 https://bit.ly/3R9pSfZ
-
#Dropbox cut its backend monorepo from 87GB → 20GB.📉
In collaboration with #GitHub, they fixed a massive bottleneck by optimizing Git delta compression.
The impact:
• Reduced clone times
• Improved CI performance
• Boosted developer velocityLearn more 👉 https://bit.ly/3R9pSfZ
-
#Dropbox cut its backend monorepo from 87GB → 20GB.📉
In collaboration with #GitHub, they fixed a massive bottleneck by optimizing Git delta compression.
The impact:
• Reduced clone times
• Improved CI performance
• Boosted developer velocityLearn more 👉 https://bit.ly/3R9pSfZ
-
#Dropbox cut its backend monorepo from 87GB → 20GB.📉
In collaboration with #GitHub, they fixed a massive bottleneck by optimizing Git delta compression.
The impact:
• Reduced clone times
• Improved CI performance
• Boosted developer velocityLearn more 👉 https://bit.ly/3R9pSfZ
-
Reducing our #monorepo size to improve developer velocity
https://dropbox.tech/infrastructure/reducing-our-monorepo-size-to-improve-developer-velocity
-
Reducing our #monorepo size to improve developer velocity
https://dropbox.tech/infrastructure/reducing-our-monorepo-size-to-improve-developer-velocity
-
Reducing our #monorepo size to improve developer velocity
https://dropbox.tech/infrastructure/reducing-our-monorepo-size-to-improve-developer-velocity
-
Reducing our #monorepo size to improve developer velocity
https://dropbox.tech/infrastructure/reducing-our-monorepo-size-to-improve-developer-velocity
-
Reducing our #monorepo size to improve developer velocity
https://dropbox.tech/infrastructure/reducing-our-monorepo-size-to-improve-developer-velocity
-
Tour d'horizon des workspaces npm.
🔗 https://wasp.sh/blog/2026/03/25/gentle-intro-npm-workspaces
-
Tour d'horizon des workspaces npm.
🔗 https://wasp.sh/blog/2026/03/25/gentle-intro-npm-workspaces
-
Tour d'horizon des workspaces npm.
🔗 https://wasp.sh/blog/2026/03/25/gentle-intro-npm-workspaces
-
Tour d'horizon des workspaces npm.
🔗 https://wasp.sh/blog/2026/03/25/gentle-intro-npm-workspaces
-
🚀 Heading to Istanbul for @teknasyon meetup on April 11th!
I'll be talking about Monorepos - from architecture to tooling, CI/CD strategies, and real-world migration stories.
6 years of monorepo experience packed into one talk 📦
See you there! 👉 https://meetup.teknasyon.com/
-
🚀 Heading to Istanbul for @teknasyon meetup on April 11th!
I'll be talking about Monorepos - from architecture to tooling, CI/CD strategies, and real-world migration stories.
6 years of monorepo experience packed into one talk 📦
See you there! 👉 https://meetup.teknasyon.com/
-
🚀 Heading to Istanbul for @teknasyon meetup on April 11th!
I'll be talking about Monorepos - from architecture to tooling, CI/CD strategies, and real-world migration stories.
6 years of monorepo experience packed into one talk 📦
See you there! 👉 https://meetup.teknasyon.com/
-
🚀 Heading to Istanbul for @teknasyon meetup on April 11th!
I'll be talking about Monorepos - from architecture to tooling, CI/CD strategies, and real-world migration stories.
6 years of monorepo experience packed into one talk 📦
See you there! 👉 https://meetup.teknasyon.com/
-
🚀 Heading to Istanbul for @teknasyon meetup on April 11th!
I'll be talking about Monorepos - from architecture to tooling, CI/CD strategies, and real-world migration stories.
6 years of monorepo experience packed into one talk 📦
See you there! 👉 https://meetup.teknasyon.com/
-
PSA: Migrating the https://thi.ng/umbrella monorepo to Codeberg, including:
- updating thousands of links in ~970 files (readme's, media, API docs/snippets in source files, examples, wiki etc.)
- updated 215 package short links to point to new locations on Codeberg
- re-configured & re-uploaded hundreds of megabytes of package API docs to https://docs.thi.ng/ (with new backlinks to Codeberg)Re: short links, for example http://thi.ng/wasm-api is an alias for the more unwieldly package homepage URL in the larger umbrella repo on Codeberg: https://codeberg.org/thi.ng/umbrella/src/branch/develop/packages/wasm-api
Along with these changes, Codeberg is also the main/default remote for this project now. I will keep the Github repo (https://github.com/thi-ng/umbrella) around for a bit longer, but will add a note in some places to say that this is only a passive mirror from now on...
This exercise has taken up most of my Sunday today, for a body of work which spans close to 10 years of my life... I had migrated this large repo already in 2024, but finally got around to "make the switch". Other thi.ng projects will be migrated over the coming weeks/months...
As always, a big thank you to all the people who've been supporting this work and its maintenance. Self-promotion is absolutely not my forte and I always have prioritized putting my energy into these projects instead. But if you in any way have benefited from these varied projects and/or want to support their ongoing development, I'd highly appreciate any donations/sponsoring via:
https://codeberg.org/thi.ng/umbrella/src/branch/develop/CONTRIBUTING.md#donations
#ThingUmbrella #Monorepo #OpenSource #Migration #Codeberg #GitHub
-
PSA: Migrating the https://thi.ng/umbrella monorepo to Codeberg, including:
- updating thousands of links in ~970 files (readme's, media, API docs/snippets in source files, examples, wiki etc.)
- updated 215 package short links to point to new locations on Codeberg
- re-configured & re-uploaded hundreds of megabytes of package API docs to https://docs.thi.ng/ (with new backlinks to Codeberg)Re: short links, for example http://thi.ng/wasm-api is an alias for the more unwieldly package homepage URL in the larger umbrella repo on Codeberg: https://codeberg.org/thi.ng/umbrella/src/branch/develop/packages/wasm-api
Along with these changes, Codeberg is also the main/default remote for this project now. I will keep the Github repo (https://github.com/thi-ng/umbrella) around for a bit longer, but will add a note in some places to say that this is only a passive mirror from now on...
This exercise has taken up most of my Sunday today, for a body of work which spans close to 10 years of my life... I had migrated this large repo already in 2024, but finally got around to "make the switch". Other thi.ng projects will be migrated over the coming weeks/months...
As always, a big thank you to all the people who've been supporting this work and its maintenance. Self-promotion is absolutely not my forte and I always have prioritized putting my energy into these projects instead. But if you in any way have benefited from these varied projects and/or want to support their ongoing development, I'd highly appreciate any donations/sponsoring via:
https://codeberg.org/thi.ng/umbrella/src/branch/develop/CONTRIBUTING.md#donations
#ThingUmbrella #Monorepo #OpenSource #Migration #Codeberg #GitHub
-
PSA: Migrating the https://thi.ng/umbrella monorepo to Codeberg, including:
- updating thousands of links in ~970 files (readme's, media, API docs/snippets in source files, examples, wiki etc.)
- updated 215 package short links to point to new locations on Codeberg
- re-configured & re-uploaded hundreds of megabytes of package API docs to https://docs.thi.ng/ (with new backlinks to Codeberg)Re: short links, for example http://thi.ng/wasm-api is an alias for the more unwieldly package homepage URL in the larger umbrella repo on Codeberg: https://codeberg.org/thi.ng/umbrella/src/branch/develop/packages/wasm-api
Along with these changes, Codeberg is also the main/default remote for this project now. I will keep the Github repo (https://github.com/thi-ng/umbrella) around for a bit longer, but will add a note in some places to say that this is only a passive mirror from now on...
This exercise has taken up most of my Sunday today, for a body of work which spans close to 10 years of my life... I had migrated this large repo already in 2024, but finally got around to "make the switch". Other thi.ng projects will be migrated over the coming weeks/months...
As always, a big thank you to all the people who've been supporting this work and its maintenance. Self-promotion is absolutely not my forte and I always have prioritized putting my energy into these projects instead. But if you in any way have benefited from these varied projects and/or want to support their ongoing development, I'd highly appreciate any donations/sponsoring via:
https://codeberg.org/thi.ng/umbrella/src/branch/develop/CONTRIBUTING.md#donations
#ThingUmbrella #Monorepo #OpenSource #Migration #Codeberg #GitHub
-
PSA: Migrating the https://thi.ng/umbrella monorepo to Codeberg, including:
- updating thousands of links in ~970 files (readme's, media, API docs/snippets in source files, examples, wiki etc.)
- updated 215 package short links to point to new locations on Codeberg
- re-configured & re-uploaded hundreds of megabytes of package API docs to https://docs.thi.ng/ (with new backlinks to Codeberg)Re: short links, for example http://thi.ng/wasm-api is an alias for the more unwieldly package homepage URL in the larger umbrella repo on Codeberg: https://codeberg.org/thi.ng/umbrella/src/branch/develop/packages/wasm-api
Along with these changes, Codeberg is also the main/default remote for this project now. I will keep the Github repo (https://github.com/thi-ng/umbrella) around for a bit longer, but will add a note in some places to say that this is only a passive mirror from now on...
This exercise has taken up most of my Sunday today, for a body of work which spans close to 10 years of my life... I had migrated this large repo already in 2024, but finally got around to "make the switch". Other thi.ng projects will be migrated over the coming weeks/months...
As always, a big thank you to all the people who've been supporting this work and its maintenance. Self-promotion is absolutely not my forte and I always have prioritized putting my energy into these projects instead. But if you in any way have benefited from these varied projects and/or want to support their ongoing development, I'd highly appreciate any donations/sponsoring via:
https://codeberg.org/thi.ng/umbrella/src/branch/develop/CONTRIBUTING.md#donations
#ThingUmbrella #Monorepo #OpenSource #Migration #Codeberg #GitHub
-
PSA: Migrating the https://thi.ng/umbrella monorepo to Codeberg, including:
- updating thousands of links in ~970 files (readme's, media, API docs/snippets in source files, examples, wiki etc.)
- updated 215 package short links to point to new locations on Codeberg
- re-configured & re-uploaded hundreds of megabytes of package API docs to https://docs.thi.ng/ (with new backlinks to Codeberg)Re: short links, for example http://thi.ng/wasm-api is an alias for the more unwieldly package homepage URL in the larger umbrella repo on Codeberg: https://codeberg.org/thi.ng/umbrella/src/branch/develop/packages/wasm-api
Along with these changes, Codeberg is also the main/default remote for this project now. I will keep the Github repo (https://github.com/thi-ng/umbrella) around for a bit longer, but will add a note in some places to say that this is only a passive mirror from now on...
This exercise has taken up most of my Sunday today, for a body of work which spans close to 10 years of my life... I had migrated this large repo already in 2024, but finally got around to "make the switch". Other thi.ng projects will be migrated over the coming weeks/months...
As always, a big thank you to all the people who've been supporting this work and its maintenance. Self-promotion is absolutely not my forte and I always have prioritized putting my energy into these projects instead. But if you in any way have benefited from these varied projects and/or want to support their ongoing development, I'd highly appreciate any donations/sponsoring via:
https://codeberg.org/thi.ng/umbrella/src/branch/develop/CONTRIBUTING.md#donations
#ThingUmbrella #Monorepo #OpenSource #Migration #Codeberg #GitHub
-
Согласованность API по принципу единого источника истины
Представим ситуацию: идет тяжёлый спринт, вы выполнили кучу задач, написали тонну нового функционала, готовитесь к релизу и вдруг обнаруживайте, что часть фич перестала работать! Идёте разбираться и обнаруживайте, что оказывается бэкендер Вася в последний момент решил переименовать поля в json-е, а вам об этом не сказал! Ситуация образная, но позволяет быстро обрисовать одну из болей во время разработки. В этой статье я бы хотел рассказать об одном из вариантов её решения в коде с помощью подхода Единого источника истины(Single source of truth).
https://habr.com/ru/articles/1003398/
#API #honojs #zod #RPC #SSOT #OpenAPI #typescript #monorepo #javascript
-
Согласованность API по принципу единого источника истины
Представим ситуацию: идет тяжёлый спринт, вы выполнили кучу задач, написали тонну нового функционала, готовитесь к релизу и вдруг обнаруживайте, что часть фич перестала работать! Идёте разбираться и обнаруживайте, что оказывается бэкендер Вася в последний момент решил переименовать поля в json-е, а вам об этом не сказал! Ситуация образная, но позволяет быстро обрисовать одну из болей во время разработки. В этой статье я бы хотел рассказать об одном из вариантов её решения в коде с помощью подхода Единого источника истины(Single source of truth).
https://habr.com/ru/articles/1003398/
#API #honojs #zod #RPC #SSOT #OpenAPI #typescript #monorepo #javascript
-
Согласованность API по принципу единого источника истины
Представим ситуацию: идет тяжёлый спринт, вы выполнили кучу задач, написали тонну нового функционала, готовитесь к релизу и вдруг обнаруживайте, что часть фич перестала работать! Идёте разбираться и обнаруживайте, что оказывается бэкендер Вася в последний момент решил переименовать поля в json-е, а вам об этом не сказал! Ситуация образная, но позволяет быстро обрисовать одну из болей во время разработки. В этой статье я бы хотел рассказать об одном из вариантов её решения в коде с помощью подхода Единого источника истины(Single source of truth).
https://habr.com/ru/articles/1003398/
#API #honojs #zod #RPC #SSOT #OpenAPI #typescript #monorepo #javascript
-
Согласованность API по принципу единого источника истины
Представим ситуацию: идет тяжёлый спринт, вы выполнили кучу задач, написали тонну нового функционала, готовитесь к релизу и вдруг обнаруживайте, что часть фич перестала работать! Идёте разбираться и обнаруживайте, что оказывается бэкендер Вася в последний момент решил переименовать поля в json-е, а вам об этом не сказал! Ситуация образная, но позволяет быстро обрисовать одну из болей во время разработки. В этой статье я бы хотел рассказать об одном из вариантов её решения в коде с помощью подхода Единого источника истины(Single source of truth).
https://habr.com/ru/articles/1003398/
#API #honojs #zod #RPC #SSOT #OpenAPI #typescript #monorepo #javascript
-
This is your semi-random reminder that #monorepo > #manyrepo.
I just made my life *much* easier by force merging three repos into one. No more deps build & publish & updates & ... No more 3 ways to do one thing. No more sync-somehow-and-hope-for-the-best on projects.
Seriously if I could, I would just put *every* single thing I'm working on into one giant git repository and remove so much unnecessary engineering masturbation from my life.
-
This is your semi-random reminder that #monorepo > #manyrepo.
I just made my life *much* easier by force merging three repos into one. No more deps build & publish & updates & ... No more 3 ways to do one thing. No more sync-somehow-and-hope-for-the-best on projects.
Seriously if I could, I would just put *every* single thing I'm working on into one giant git repository and remove so much unnecessary engineering masturbation from my life.
-
This is your semi-random reminder that #monorepo > #manyrepo.
I just made my life *much* easier by force merging three repos into one. No more deps build & publish & updates & ... No more 3 ways to do one thing. No more sync-somehow-and-hope-for-the-best on projects.
Seriously if I could, I would just put *every* single thing I'm working on into one giant git repository and remove so much unnecessary engineering masturbation from my life.
-
This is your semi-random reminder that #monorepo > #manyrepo.
I just made my life *much* easier by force merging three repos into one. No more deps build & publish & updates & ... No more 3 ways to do one thing. No more sync-somehow-and-hope-for-the-best on projects.
Seriously if I could, I would just put *every* single thing I'm working on into one giant git repository and remove so much unnecessary engineering masturbation from my life.
-
This is your semi-random reminder that #monorepo > #manyrepo.
I just made my life *much* easier by force merging three repos into one. No more deps build & publish & updates & ... No more 3 ways to do one thing. No more sync-somehow-and-hope-for-the-best on projects.
Seriously if I could, I would just put *every* single thing I'm working on into one giant git repository and remove so much unnecessary engineering masturbation from my life.
-
So #monorepo is a thing. And from my experience makes every project better.
Wouldn't it make sense to also make #monocontainer?
- There are caches on multiple layers already, so I would not expect build time to go up.
- I would guess storage space requirements should go down as one needs to build & hold only one thing.
- The shenanigans of setting up a-thing in multiple containers falling into multiple traps would just go away. -
So #monorepo is a thing. And from my experience makes every project better.
Wouldn't it make sense to also make #monocontainer?
- There are caches on multiple layers already, so I would not expect build time to go up.
- I would guess storage space requirements should go down as one needs to build & hold only one thing.
- The shenanigans of setting up a-thing in multiple containers falling into multiple traps would just go away. -
So #monorepo is a thing. And from my experience makes every project better.
Wouldn't it make sense to also make #monocontainer?
- There are caches on multiple layers already, so I would not expect build time to go up.
- I would guess storage space requirements should go down as one needs to build & hold only one thing.
- The shenanigans of setting up a-thing in multiple containers falling into multiple traps would just go away. -
So #monorepo is a thing. And from my experience makes every project better.
Wouldn't it make sense to also make #monocontainer?
- There are caches on multiple layers already, so I would not expect build time to go up.
- I would guess storage space requirements should go down as one needs to build & hold only one thing.
- The shenanigans of setting up a-thing in multiple containers falling into multiple traps would just go away. -
So #monorepo is a thing. And from my experience makes every project better.
Wouldn't it make sense to also make #monocontainer?
- There are caches on multiple layers already, so I would not expect build time to go up.
- I would guess storage space requirements should go down as one needs to build & hold only one thing.
- The shenanigans of setting up a-thing in multiple containers falling into multiple traps would just go away. -
How We Synchronize .NET’s Virtual Monorepo
https://devblogs.microsoft.com/dotnet/how-we-synchronize-dotnets-virtual-monorepo/#microsoft #NET #NET_Internals #Developer_Stories #git #Infrastructure #Monorepo #Source_Control #VMR
-
How We Synchronize .NET’s Virtual Monorepo
https://devblogs.microsoft.com/dotnet/how-we-synchronize-dotnets-virtual-monorepo/#microsoft #NET #NET_Internals #Developer_Stories #git #Infrastructure #Monorepo #Source_Control #VMR
-
Everything as Code: How We Manage Our Company in One Monorepo
https://www.kasava.dev/blog/everything-as-code-monorepo
#HackerNews #EverythingAsCode #Monorepo #CompanyManagement #DevOps #SoftwareDevelopment
