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
Not sure if this is even possible or in scope for this action, but we install dependencies inside a Docker container where we also have our required extensions available. We can't use this action with that unfortunately. I think that if you're able to set the php/composer executable that this could work something like this:
- uses: "ramsey/composer-install@v1"with:
php: "docker-compose run --rm php"
The main reason we do it this way is because some packages install different versions depending on the php environment (like Ocramius/ProxyManager if I remember correctly). We could replicate our environment using shivammathur/setup-php of course, but that would mean maintaining our php environment in 2 places.
Is this something you'd consider?
The text was updated successfully, but these errors were encountered:
Good question, I think setting the composer executable should be enough. Then again being able to set the php executable is maybe a more portable solution. I'm not sure.
Quick update... I'll be adding php-path and composer-path input parameters, so you can set one or the other, or both. Expect to see this in (maybe) version 2.1.0.
Not sure if this is even possible or in scope for this action, but we install dependencies inside a Docker container where we also have our required extensions available. We can't use this action with that unfortunately. I think that if you're able to set the php/composer executable that this could work something like this:
The main reason we do it this way is because some packages install different versions depending on the php environment (like Ocramius/ProxyManager if I remember correctly). We could replicate our environment using
shivammathur/setup-php
of course, but that would mean maintaining our php environment in 2 places.Is this something you'd consider?
The text was updated successfully, but these errors were encountered: