Skip to content
This repository has been archived by the owner on Oct 13, 2023. It is now read-only.

Best practices for private composer packages and upgrades #27

Open
colinmurphy opened this issue May 21, 2021 · 0 comments
Open

Best practices for private composer packages and upgrades #27

colinmurphy opened this issue May 21, 2021 · 0 comments

Comments

@colinmurphy
Copy link

I was wondering is there any best practices around Composer and private or paid packages.

So the problem is that when you go to upgrade Shopware to a major version is that the composer.json file generally contains some paid packages and private packages.

Our solution so far has been to copy the composer.json and composer.lock directly from production and then run composer install and we then add back in the paid and private packages.

However this is time consuming and requires comparing the original composer.json file. I wanted to see is there a better way of adding paid and private packages so that when you do need to upgrade Shopware it can be a lot less time consuing.

Thanks,
Colin

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant