w0rd-driven
commented
2 years ago Another option I just remembered would be Laravel Sail with my recent Laravel on Fly.io attempt that is pretty much a straight up copy with a few adjustments to include Nginx and other production-ready alternatives.
I would personally recommend Laravel Sail or Server Side Up's implementations as they should be heavily maintained moving forward.
Since I don't know how long I plan on being active in the Laravel ecosystem I thought it would be prudent to look for alternatives to either replace this project outright or simplify things slightly away from the default PHP images.
The new image to try is at https://github.com/serversideup/docker-php or https://hub.docker.com/r/serversideup/php/. It would be worth trying to get one of the particularly nasty CI builds that require the most PHP extensions to see how it fares.
There's always the option my coworker took: to use the base image in Gitlab CI and add all the customization options in the various setup shell scripts. Installing additional PHP extensions is outlined at https://github.com/serversideup/docker-php#other-customizations.
It's always preferred to "bake in" all of the OS package network requests and installation to reduce time to completion but no one I work with would complain if jobs took the standard 5 minutes to complete vs 1.5 minutes or whatever it's actually reduced to. There may be clever caching techniques to mitigate some of this that I've never really considered.
Lastly, I'm also open to deprecating this in favor of someone forking it. I don't want to transfer ownership primarily because I don't know what that would do for Docker Hub and Gitlab CI. Breaking the majority of our existing repositories, something I would have to fix is not something I'm keen on putting on my plate now or in the future. I will gladly point to your repository when I've archived this one as read-only unless you have a better alternative.