joseph.olstad's sandbox: boost_blast

NOTE: there is a related patch available for boost that we have not yet tested that might make this module unnecessary: https://www.drupal.org/node/2277703#comment-8941407

We have created a custom module called "BOOST BLAST" that is designed to work with boost and expire. If you want something similar for varnish, please have a look at varnish_vanish which was initially a port from boost_blast.

Why BOOST BLAST ?

we have multiple aliases for our site
xyz.com
xyz.net
xyz.ca
xyz.org
xyz-yzy.com
xyz-yzy.net
xyz-yzy.ca
xyz-yzy.org

without our BOOST BLAST module cache is only expired in either the $base_url or if not using $base_url then only from the alias from which the content was deployed to and from.

Explanation:
assuming boost_cache_dir is sites/all/cache
assuming boost_normal_dir is normal

the following folders will be created as visitors visit all the aliases:
example:
sites/all/cache/normal
sites/all/cache/normal/xyz.com
sites/all/cache/normal/xyz.net
sites/all/cache/normal/xyz.ca
sites/all/cache/normal/xyz.org
sites/all/cache/normal/xyz-yzy.com
sites/all/cache/normal/xyz-yzy.net
sites/all/cache/normal/xyz-yzy.ca
sites/all/cache/normal/xyz-yzy.org

without this module content publishers will publish on internal-xyz.com , the problem is, only sites/all/cache/normal/internal-xyz.com will be BLASTed , leaving outdated content in the other caches for the other aliases.

with BOOST BLAST and the 'expire' module when content publishers publish or update content ALL CONFIGURED BOOST CACHES for ALL site aliases are BLASTED.
example:
sites/all/cache/normal
sites/all/cache/normal/xyz.com
sites/all/cache/normal/xyz.net
sites/all/cache/normal/xyz.ca
sites/all/cache/normal/xyz.org
sites/all/cache/normal/xyz-yzy.com
sites/all/cache/normal/xyz-yzy.net
sites/all/cache/normal/xyz-yzy.ca
sites/all/cache/normal/xyz-yzy.org

will be BLASTed

expire is a dependency, configuration applies, you choose when you want expire to blast

BOOST BLAST will then allow you to keep unlimited cache limits and only expire when new content is published/or existing content is updated. cache folders for all aliases are blasted and will let boost rebuild the cache and continue doing what boost does.

This module works on normal single site operation (without deploy/syndication)
AND it works with source and destination sites (using deploy/syndication) (provided that BOOST BLAST is installed and configured on source and dest.)