I would not suggest it that way. Its better to isolate http,php layers. Now they are cramed up in a single docker layer named wordpress. Why is that because you can test performance with different http services at the same time. As well usually you'd know which layer ir responsible for server side problems. Am I wrong?
I don't fully understand what you mean.
This is based on the offical WordPress docker image.
Also it is a setup for development.
Why should I at this point care about the http performance?
If I want to have something that scales I can just spin up multiple instances of the docker image.
You get the usual logs as with every service so you could just look into the logs.
For me this is the wrong point in time to think about http performance but we can have a talk about that.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.