Open pvdleek opened 1 week ago
It sounds not bad. I'm thinking of something like an ENV to pass a list of extensions (not just PSR) to disable at start-up (remove them eventually).
On the other hand, being able to turn off extensions at build time should be also a nice feature since not all users want the same amount of extensions to use.
Feel free to propose something in either case.
I think an ENV would do just fine. At this point I would go for a blacklist to disable certain extensions. So in my case I would pass on an ENV "EXTENSION_BLACKLIST" with value "psr" or something like that. In the mean time I made a copy of this repo, removed PSR and published my own base-image, but I'd rather go back to this repo with the possibility to disable PSR ;)
Hi, I ran into an issue today that the PSR extension conflicts with the Symfony cache component. I therefore had to remove PSR, but as there is no "docker-php-ext-disable" (and it will not be there, see https://github.com/docker-library/php/issues/220#issuecomment-353677238) I tried "pecl uninstall psr". Unfortunately that created another issue:
I could of course create a PR for the removal of PSR, but it might be more interesting to have a ENV variable control the installation of PSR (and maybe other extensions).
How do you feel about this?