Trellis already offers intelligent full page caching (nginx microcaching), so static pages are already covered.
MariaDB already uses InnoDB by default, so this is also covered.
For object caching , using trellis-redis and WP Redis gave a significant perofrmance increase.
Now dynamic pages like of WooCommerce can’t be cached, they even have to be excluded from microcaching . However, it is possible to cache specific page parts that don’t change (often), that would be page part caching.Varnish with some WordPress Varnish integration plugin be an option?
Related discussions:
Does anyone have some experience with setting up Varnish to sit in front of nginx as it is configured through trellis? I’m having issues trying to discover where to point Varnish at with trellis. Varnish accepts a “back-end” hostname and I have not been able to get trellis to serve content to varnish through IP (since it would seem trellis does not support this - no IP accessibility unless through FQDN.
I’ve tried running nginx on different ports and configuring Varnish on the same machine (not…
That’s exactly what I did. The problem is WordPress (via redirect_canonical I think) does a 301 redirect when it sees that the port doesn’t match.
Tried adding port_in_redirect off; to nginx server block but it didn’t seem to help…
And the funny thing is I already strip off the port from HTTP Host header in my .vcl file. Should I not be doing that? (Oh wait… This only matters if the request URL from browser contains a port number. Nevermind…)