Open alinceDev opened 9 months ago
Usually, The structure as following:
|- monrepo
|- packages
|- mylib1
composer.json
|- mylib2
composer.json
composer.json
merge composer context of all packages into the main composer.json (installed monorepo in this)
In the other project
|- web
|- app
composer.json
composer.lock
Install own libs
Ok, in my case I have this structure :
|- monrepo
|- packages
|- myBundle
composer.json
|- web
|- app
composer.json => myBundle
composer.lock
|- app2
composer.json => myBundle
composer.lock
|- app3
composer.json => myBundle
composer.lock
......
composer.json
In that case, monorepo-builder is not adapted for that ?
Hi,
I don't get the point here. Say we have the following structure :
So when I release a version, all the dependencies are updated, but not the composer.lock. So in a CI I can't do a composer install. How do you handle this ? I also read this blog but not helped me https://blog.logrocket.com/hosting-all-your-php-packages-together-in-a-monorepo/
Thanks