Too dependent
-
This plugin is not an standalone plugin. You need to fully install their server and replace the Apache/Nginx you have, wich is very tedious. Also there’s an option to use their CDN and avoid to change the server, but is not free. If your server has a few visits maybe will work, but after 1 GB you have to purchase more traffic.
-
All what I’ve said is true, so I’ve Read, Understood and then I speak. Is too dependant because you have to install their service in your server if you want the full functionality without external CDN (doesn’t care that free version exists, is a big change and very tedious). If you don’t want to do it, then to make it work correctly you have to use their CDN services because is how is done… it implement the CDN invalidation only for their CDN services and when the 1gb free is used, the plugin becomes not useful because the CDN is disabled.
To add a CloudFlare in front I don’t need a plugin, because the invalidation is not implemented and I have to invalidate the CDN manually every time I change anything, so again, this pluging is not useful at all. Nothing changes if I use their CDN together with the CloudFlare CDN.
Understanding that, is not an stanadalone plugin and needs some special things to make it work. There are a lot of plugins that works by itself without anything external, like for example W3Total-Cache that even implement CDN invalidation and Varnish support.
I’m just saving time to people that doesn’t now all this and doesn’t want to change all this.
Have a nice day.
The topic ‘Too dependent’ is closed to new replies.
