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
GeneratedExtensionsConfig.php is generated in vendor/infection/extension-installer/src/GeneratedExtensionsConfig.php.
But of some projects we don't have the permission to write in this directory.
For example I install infection as composer global in a Docker image with root user then when i use this image with anoher user (same as host user, generally 1000:1000) he don't have permission to write in this directory.
Can I change this directory?
If not, can you provide a configuration to do that, or maybe use config.cache-dir configuration in composer.json?
The text was updated successfully, but these errors were encountered:
Hi, can you then use PHAR distribution of Infection instead of a global composer package?
In PHAR, all extensions are preinstalled, so you won't have such issue.
Can I change this directory?
it's not supported right now
If not, can you provide a configuration to do that, or maybe use config.cache-dir configuration in composer.json?
From the first look, I don't see how to do it, because now generated class is Infection\ExtensionInstaller\GeneratedExtensionsConfig and it works out of the box by utilizing PSR-4 autoloader. If we would move it outside of composer's vendor directory, PSR-4 wont' work anymore.
Hi,
GeneratedExtensionsConfig.php
is generated invendor/infection/extension-installer/src/GeneratedExtensionsConfig.php
.But of some projects we don't have the permission to write in this directory.
For example I install infection as
composer global
in a Docker image withroot
user then when i use this image with anoher user (same as host user, generally1000:1000
) he don't have permission to write in this directory.Can I change this directory?
If not, can you provide a configuration to do that, or maybe use
config.cache-dir
configuration incomposer.json
?The text was updated successfully, but these errors were encountered: