Hi everyone,
I want to start by saying that I do not consider Mush a replacement for BPKG. I still use and appreciate BPKG for my projects. The primary goal of Mush is to introduce tools that enhance the organization of shell projects.
With that in mind, I would like to present the concept of the Distributed Registry in Mush. This is an alternative approach that complements the ongoing efforts to support GitLab integration.
The Distributed Registry is a decentralized system where packages are hosted on multiple Git nodes, each managed by its own maintainer. This approach ensures greater flexibility, scalability, and community involvement, without relying on a proprietary CDN.
Your feedback and insights are incredibly valuable to me, and I cherish your opinions. Thank you for your continuous support and hard work.
For more details on how the Distributed Registry is implemented in Mush, please refer to the concept of Distributed Registry in Mush.
Best regards,
Francesco Bianco
cc
@Potherca
@jwerle
Hi everyone,
I want to start by saying that I do not consider Mush a replacement for BPKG. I still use and appreciate BPKG for my projects. The primary goal of Mush is to introduce tools that enhance the organization of shell projects.
With that in mind, I would like to present the concept of the Distributed Registry in Mush. This is an alternative approach that complements the ongoing efforts to support GitLab integration.
The Distributed Registry is a decentralized system where packages are hosted on multiple Git nodes, each managed by its own maintainer. This approach ensures greater flexibility, scalability, and community involvement, without relying on a proprietary CDN.
Your feedback and insights are incredibly valuable to me, and I cherish your opinions. Thank you for your continuous support and hard work.
For more details on how the Distributed Registry is implemented in Mush, please refer to the concept of Distributed Registry in Mush.
Best regards,
Francesco Bianco
cc
@Potherca
@jwerle