The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.I need to run cron twice hourly (large amount of aggregated content). This becomes problematic with a one hour cache lifetime. If an expired cache clear was integrated into drush, this would facilitate a periodic cron job to clear the stale files. I wasn't sure to file this under code or UI. My apologies if I made the wrong choice.
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | boost-517962.patch | 3.13 KB | mikeytown2 |
| #9 | boost.drush_.inc_.txt | 2.29 KB | sillygwailo |
Comments
Comment #1
mikeytown2 commentedIs the problem that you only want cron to flush expired content? Current solution is to run a modified cron
http://drupal.org/node/331537
Related: http://drupal.org/node/19173
Is this what you where looking for?
Comment #2
mikeytown2 commentedhttp://www.opensourcery.com/blog/dylan-tack/choosier-cron-runs
http://drupal.org/project/elysia_cron
http://drupal.org/project/supercron
Comment #3
mikeytown2 commentedhttp://drupal.org/project/provision_boost
Comment #4
dbeall commentedadded to handbook, Tips and Tricks page
Comment #6
sillygwailoI'm not convinced that the Provision Boost Support module currently provides the functionality asked for here. It "only" provides verify for the Aegir system. I think what eyecon wants (correct me if I'm wrong) is integration that would provide a cache-clear command specific to Boost for Drush. Something along the lines of:
drush -l http://example.com/ boost-cache-clear-allOR
drush -l http://example.com/ boost-cache-clear-expiredIf it's using one of the solutions to run a stripped-down cron, then we'd need specific documentation to that effect. So I think that in the handbook, as written, the proposed solution doesn't solve the problem.
Comment #7
sillygwailoComment #8
noslokire commented+1
Comment #9
sillygwailoAttached is a
boost.drush.incfile (remove the .txt extension and the underscore) to drop in with the module package. It adds the following Drush commands:Tested against 6.x-1.8 and 6.x-dev (as of yesterday) and Drush 3.3. Development sponsored by OpenRoad Communications.
Comment #10
mikeytown2 commentedmodified the drush commands so they should almost always work (just as if you did the commands from the admin section of the module page).
Comment #11
mikeytown2 commentedcommitted. Thanks for the patch!
Comment #13
geerlingguy commentedIs there any way this functionality could be added back in for the D7 version?
Comment #14
Anonymous (not verified) commentedI'll have a look, it make a nice change to work on something a little different within drupal.
Comment #15
socialnicheguru commentedReviving this after two years.
This would make a nice addition to drush.
Comment #17
bgm commentedI committed a basic implementation in 7.x-1.x. Please review/test/improve.
Comment #18
yannisc commentednice! thank you!
When will there be a new release that will have this in?
Comment #19
grn commentedThis is not in the latest dev, right?