-
Be the first to like this
Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Published on
The development of multiple repositories is not always an easy task. If you want to offer a high-quality and evolving application, sooner or later, there is a need to make the same changes in several packages. This can be a simple change in the documentation of a few packages or the adoption of new coding standards. During the development of Shopsys Framework, we have come to the point where thousands of hours were allocated for development across multiple repositories and for development of new packages. And it was this moment when we decided to choose the way of monorepo. Upgrade several packages to a new version of PHPUnit? Why not! Change of method in API used across multiple packages? Super easy! Of course, monorepo is not for everyone. We will show you, why it can be useful to use monorepo and what was the way to the monorepo in Shopsys Framework.
Be the first to like this
Login to see the comments