-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
move file cache to generated/metadata #13
base: master
Are you sure you want to change the base?
Conversation
move file cache to generated/metadata to fix issue sin magento cloud and use standard location
This is not only an issue with Magento Cloud, but also with the --keep-generated parameter for bin/magento setup:upgrade. I think for now, we should also just change the clean() method in vendor/creatuity/magento2-interceptors/Generator/FileCache.php and let it return true or false or base it if we are on production mode or not:
Unless we want these generated plugin files to be removed? But then I fear they might not get regenerated when in production mode, so after the usage of bin/magento setup:upgrade --keep-generated, which we also use in our deploy scripts next to a regular bin/magento setup:upgrade before that. In order to check for PROD mode or not, you probably need to change the following?
and
I will do some tests with this. |
@igorwulff , as we're facing the same issue: Were you able to test this and find a good solution? |
Hi @norgeindian I haven't tested this in production unfortunately. I still think it is an good way to approach the problem. |
Move file cache to generated/metadata to fix issues in magento cloud and use standard location
note: tests are required before merging this.