A bit more context on the “runtime” part, because this turned into a bigger rabbit hole than just building Docker images. The images dogfood three other Cbox projects: cbox-init is PID 1 and handles process supervision, dependencies, health/readiness, graceful shutdown, hooks, etc.
github.com/cboxdk/init fpm-tune measures actual PHP-FPM worker memory/CPU usage and adjusts pm.max_children from the workload it sees, rather than guessing a number upfront.
github.com/cboxdk/fpm-tune fpm-exporter exposes FPM, Opcache and Laravel metrics to Prometheus.
github.com/cboxdk/fpm-export… The dogfooding part has probably been the most useful bit. Running these together has already exposed real bugs and edge cases in the individual projects, which then get fixed upstream and fed back into the images. So while php-baseimages started because I was tired of installing the same extensions and fixing the same container/permission issues, it has gradually become the integration point for how I think a boring, observable PHP-FPM runtime should work.

@tibbsa As you commented on the last post, CPU is now fully supported as well. :)

A bit of context: this started as tuning logic inside my PID 1/init package. I pulled it out, iterated on it quite a bit, and made it standalone so it can run alongside existing setups too. Forge, Ploi, regular VMs, etc. Same idea, without needing my whole runtime 🙂