Use env for package version #12434
Replies: 1 comment 1 reply
-
|
This would make the composer.lock file unreliable, as it would depend on the value of the env variable on the system running To me, this looks like a no-go (but I'll let the maintainers take a final decision, as I'm only an active contributor). Btw, what is your use case for have a version constraint of a package in your docker-compose file (remembering that a version constraint is not the same than the version of the installed package) ? |
Beta Was this translation helpful? Give feedback.
-
|
I tend to agree here, this sounds like in such a case you probably should generate the composer.json using the env var and some script, run composer against that, then it's your responsibility to deal with the fallout.. Building this into Composer sounds too messy :) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I have many places where i maintain a package version.
docker-composefilecomposer.jsonI would centrailze it to one
.envfile.Question: Is it possible to use env variables for a package version?
Beta Was this translation helpful? Give feedback.
All reactions