In admin/settings/varnish, the 'Selective' option of Varnish Cache Clearing says it's experimental. So is the whole module not safe to use for live production use, or only parts of it?
For example, is it safe to use for someone who needs only basic functionality of when a single node is updated, then only THAT node in Varnish should be flushed and not every one of the 10s of 1000s of nodes that could potentially be cached in Varnish at that time? Without this functionality, the Varnish module is essentially useless for a site that has regular updates to nodes! So some guidance on whether parts of this module are safe to use for production can increase adoption of this module and of Varnish. And some guidance on what parts of this module are still experimental or unsafe will allow people like me to dig through the code and submit patches.
Comments
Comment #1
mgiffordThis is still an issue. Updating version number.
A clarification about the status would be useful.
Comment #2
spleshkaIsn't it a Varnish module issue?
Comment #3
mgiffordTrue enough. Thanks!
modules/contrib/varnish/varnish.admin.inc: $form['varnish_cache_clear']['#options'][VARNISH_SELECTIVE_CLEAR] = t('Selective (experimental; uses expire.module)');
So, why is this still experimental? I would have thought that running Cache expiration was a best practice with the Varnish module.
Comment #4
misc commentedClosing issues that had no activity the latest year, please re-open if the issues is still relevant.