You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 13, 2023. It is now read-only.
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
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
The text was updated successfully, but these errors were encountered: