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
Is there any plans to do it or should we do it ourselves? If so, is there any guidelines for someone that has only been in the docker/server world for a short time. I am trying to create a small production image because the current php-apache is around 500 MB.
The text was updated successfully, but these errors were encountered:
Currently I think it is because the apache part is taken directly from Debian and so it has things that users are used to existing in their php/apache world, which would not necessarily be the case in an alpine version. Also, since the Alpine variants exist mostly for size concerned users, then they would be better served with fpm and something like nginx in front of it.
Given the complexity involved in duplicating Debian's Apache configuration and usage for Alpine, I don't think this is going to be solved any time soon.
The best advice I can give is to either use the Debian version (since the size difference is not that dramatic, given today's normal storage and bandwidth availability), or to use FPM (which is also much more in the spirit of Alpine's minimalism). Thanks! ❤️
I've just opened a PR with this functionality #1222
I have a project that I would prefer to use apache rather than nginx and the debian based apache variant is quite a large image. Given the changes were relatively minor to get this running I hope it can be accepted
Is there any plans to do it or should we do it ourselves? If so, is there any guidelines for someone that has only been in the docker/server world for a short time. I am trying to create a small production image because the current php-apache is around 500 MB.
The text was updated successfully, but these errors were encountered: