4 ms·

At least when using nginx you don't even need WP Super Cache or any other Wordpress plugin. Instead you can utilize Nginx' FastCGI cache feature [1] which works

At least when using nginx you don't even need WP Super Cache or any other Wordpress plugin. Instead you can utilize Nginx' FastCGI cache feature [1] which works for anything using FastCGI and not just Wordpress. Here is an example for a tutorial on how to configure the FastCGI cache for Wordpress: https://easyengine.io/wordpress-nginx/tutorials/single-site/fastcgi-cache-with-purging/ https://easyengine.io/wordpress-nginx/tutorials/single-site/... [1]: https://nginx.org/en/docs/http/ngx_http_fastcgi_module.html#fastcgi_cache https://nginx.org/en/docs/http/ngx_http_fastcgi_module.html#...

Neil44 5y ago
You would have to configure that carefully so that for example you didn’t cache shopping baskets.
- Dunedan 5y ago
  As shown in the linked guide you'd configure that based on something like an application specific cookie, which is probably required for the shopping basket in the first place anyway. I believe solutions like WP Super Cache handle that the same way, but I might be wrong about that.
lolinder 5y ago
Caching solves only the performance problem, which in my mind is the least compelling reason to go for static site. If your wp-admin routes are still accessible to the public internet, then you are still at risk for broken plugins causing a hack. You have to both cache all static directories and firewall the actual server if you want to avoid being hacked by one of the thousands of scripts that scans every IP address for WordPress plugin vulnerabilities.
- Dunedan 5y ago
  > Caching solves only the performance problem, which in my mind is the least compelling reason to go for static site. One the other hand there are compelling reasons for not going with a static site as well. Try getting non-technical users to write the markup for their posts by hand without a WYSIWYG editor. Or try to integrate features like comments with a static site without using a third-party service. > If your wp-admin routes are still accessible to the public internet, then you are still at risk for broken plugins causing a hack. You have to both cache all static directories and firewall the actual server if you want to avoid being hacked by one of the thousands of scripts that scans every IP address for WordPress plugin vulnerabilities. That's a risk you have with every internet facing software. Yes, static sites are great, because they greatly reduce the attack surface, but there are reasons why not every website is a statically generated site. As the comment which lead to that thread already mentioned it's quite easy to reduce the risk by keeping the number of plugins as small as possible. I run several websites powered by Wordpress since more than 15 years and so far didn't have any security incident with them.

Neil44 5y ago

You would have to configure that carefully so that for example you didn’t cache shopping baskets.

Dunedan 5y ago
As shown in the linked guide you'd configure that based on something like an application specific cookie, which is probably required for the shopping basket in the first place anyway. I believe solutions like WP Super Cache handle that the same way, but I might be wrong about that.

lolinder 5y ago

Caching solves only the performance problem, which in my mind is the least compelling reason to go for static site. If your wp-admin routes are still accessible to the public internet, then you are still at risk for broken plugins causing a hack. You have to both cache all static directories and firewall the actual server if you want to avoid being hacked by one of the thousands of scripts that scans every IP address for WordPress plugin vulnerabilities.

Dunedan 5y ago
> Caching solves only the performance problem, which in my mind is the least compelling reason to go for static site. One the other hand there are compelling reasons for not going with a static site as well. Try getting non-technical users to write the markup for their posts by hand without a WYSIWYG editor. Or try to integrate features like comments with a static site without using a third-party service. > If your wp-admin routes are still accessible to the public internet, then you are still at risk for broken plugins causing a hack. You have to both cache all static directories and firewall the actual server if you want to avoid being hacked by one of the thousands of scripts that scans every IP address for WordPress plugin vulnerabilities. That's a risk you have with every internet facing software. Yes, static sites are great, because they greatly reduce the attack surface, but there are reasons why not every website is a statically generated site. As the comment which lead to that thread already mentioned it's quite easy to reduce the risk by keeping the number of plugins as small as possible. I run several websites powered by Wordpress since more than 15 years and so far didn't have any security incident with them.