php-pm
Supported PHP version, automated builds, better tags?
It is more a question than an issue. Containers on dockerhub looks a bit outdated - maybe it is a good idea to make some automated builds on webhooks? Also supporting more specified tags (with php version - I've tried with updating php version to 7.2 but it is quite complicated) would be nice - many projects require 7.2 php version due to object typehinting.
I may help, but don't want to make something which won't be accepted later :)
Many require 7.2? Would love to see those stats. However, I agree we could setup automated builds.
Well, I didn't meant these are OS projects ;) but ocramius/proxy is very popular package, which is in almost every PHP project I am working on.
I'll try to build some alpine and debian/ubuntu based images and semi-automate them like in official php library (full-auto isn't possible due to tag naming AFAIK).
@marcj loce -> lose
what is it with the stats loosing? i think a good project and maintainer should not need to worry about this. Whoever needs this will find it. It is actually a good approach and i am giving it a shot on production.
About the 7.2 being difficult, i think it is non sense with a pinch of salt. I mean what is the error that you are getting rather?
The image should obviously be alpine, and not ubuntu mainly.
php-pm project is very interesting, but indeed, allow multiple PHP version usage (7.2, 7.3) would unlock some usages.
Looking at your file: https://github.com/php-pm/php-pm-docker/blob/fa9b3d1d86f8850bfc579c80beca752c2caca03e/build/Dockerfile-nginx#L18
Instead of using alpine and the provided php packages, why not just use the php official images?
With some automation, you could deliver multiple version thanks to this method.
Would you consider a merge request about that?
I have found the PHP packages to be very complex. If you find a multi-arch working php approach I'd be happy to consider a PR.
