4 ms·
You could just pop Varnish cache in front of Wordpress to do the same thing - any unauthenticated GET's will just hit Varnish, and come nowhere near Wordpress i
by EwanToo 14y ago
You could just pop Varnish cache in front of Wordpress to do the same thing - any unauthenticated GET's will just hit Varnish, and come nowhere near Wordpress itself.
That way you wouldn't need to worry about software updates.
- Udo 14y agoTotally. I guess I could also use some advanced Nginx directive/plugin to do that. The hack is just something that occurred to me spontaneously, it took about 2 minutes to implement, and I didn't even have to install anything :)
- EwanToo 14y agoYou could give these 2 config files a try sometime: https://github.com/ewanleith/Wordpress-Server-Configuration-Files/blob/master/nginx-caching/default.conf https://github.com/ewanleith/Wordpress-Server-Configuration-... https://github.com/ewanleith/Wordpress-Server-Configuration-Files/blob/master/nginx-caching/nginx.conf https://github.com/ewanleith/Wordpress-Server-Configuration-... Basically they make nginx cache itself, which combined with this Wordpress plugin: http://wordpress.org/extend/plugins/nginx-champuru/ http://wordpress.org/extend/plugins/nginx-champuru/ Makes things very minimal, no need for even a dedicated cache :)