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
Different projects often have different needs in term of INI config or PHP extensions.
Most of INI config customization can be done already with a project scoped php.ini.
But what about PHP extensions? what if from a project to another they are not the same? or configured differently (hello GD)?
Would be great if, instead of having Symfony CLI use the locally installed php, it used a php service configured in the docker-compose.yaml file, or directly a Dockerfile.
So the PHP itself can be customized by project.
What do you think about this idea?
The text was updated successfully, but these errors were encountered:
Supporting Docker for running PHP is something I have in my mind for a couple of months now.
Though the initial support would be a bit different allowing to play with the concept before going further.
My idea was first to allow users to register Docker images in the PHP versions store and then use them natively.
This seems simple enough (no docker compose or dockerbuild involved) but complex enough (directory mounts and port mappings) to figure out if adding this kind of support is viable or not.
Unfortunately, I didn't get much time lately to investigate this, but I'd like to explore this soon (starting end of September probably).
Different projects often have different needs in term of INI config or PHP extensions.
Most of INI config customization can be done already with a project scoped php.ini.
But what about PHP extensions? what if from a project to another they are not the same? or configured differently (hello GD)?
Would be great if, instead of having Symfony CLI use the locally installed php, it used a
php
service configured in the docker-compose.yaml file, or directly a Dockerfile.So the PHP itself can be customized by project.
What do you think about this idea?
The text was updated successfully, but these errors were encountered: