Posted by plaverty on February 16, 2011 at 10:35pm
4 followers
Jump to:
| Project: | Boost |
| Version: | 7.x-1.x-dev |
| Component: | Installation |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
| Issue tags: | cache directory, path |
Issue Summary
In my boost settings, I see a cache directory setting but no cache path setting. The cache directory just gets set in my drupal root directory. Is it possible for me to indicate that I put this cache directory somewhere else higher in the chain? Boost wants to put the cache directory in the core files directory where we upgrade drupal core. So the next time we upgrade drupal, we'd need to remember to move the cache directory into the new core directory as well. We'd like to move cache one level higher, but I don't see a way to do that in the settings.
Is there something I'm missing?
Comments
#1
Give me some examples of what your trying to do
#2
Here is our setup:
pwd
/www/data/httpd/htdocs/cms/drupal_core/drupal6
ls
3864 Dec 16 15:07 d6-test
3864 Sep 21 2009 drupal-6.13
3864 Dec 1 2009 drupal-6.14
3864 Mar 18 2010 drupal-6.15
3864 Aug 3 2010 drupal-6.16
3864 Aug 3 2010 drupal-6.17
3864 Nov 17 09:20 drupal-6.18
3864 Dec 9 10:46 drupal-6.19
3864 Feb 3 23:43 drupal-6.20
6148 Jul 22 2010 .DS_Store
32 Mar 13 2010 sites -> /www/data/httpd/htdocs/cms/sites
So each time we upgrade, we just add a new "drupal-6.x" directory. Boost wants the cache directory to be in the drupal-6.20 directory, which is my current version. However, we'd prefer to have the cache directory sit one or two levels higher, either in the "drupal_core" directory or in the "drupal6" directory.
We are a multi-site environment, if that makes any difference.
I have the Drupal 6 Performance Tips book and it shows in version 6.1-13 of Boost, a field to set the path to the cache file. I don't see that in my current version 6.1-18 of Boost. Was this taken out or am I just looking in the wrong place? Is there a way to set this? Am I going about something wrong?
Thank you!
#3
have you considered using a symlink?
#4
Heh, no. The simplest answer isn't always the most obvious. Thank you.
#5
Sorry to re-open this old thread, and please close it again if I'm just being thick, but I don't see how a symlink will solve this problem?
Yes, it means that you can store the Boost-generated files in a different location, but it still requires the site maintainer to add the symlink into the root installation folder every time they update core. Would it not be better to be able to set a path as well as a directory name, so that cached files can be stored outside of the Drupal installation, and therefore remain unaffected by core updates?
#6
If you put the files higher-up, you still need a web server setting so that those files are accessible.
i.e. if your web DocumentRoot is /var/www/drupal-7.10/, and you want your boost cache path in /var/www/cache/, then you'll need an alias in Apache to alias /cache/ to /var/www/cache.
An easy workaround, is to just create a symlink. You probably have shell scripts to deploy your platform, so it's rather trivial. You can also use an Aegir based solution with provision_boost.
I can review/commit a patch if you send one, but this seems of limited use: after upgrading the core, you should flush the cache anyway. So it makes more sense imho to just put this in your shell scripts.
#7
OK, You've sold me. Unfortunately, our deployments are only partially automated and our Development team is still quite new to Drupal. But it makes sense in terms of the module to keep things the way they are.
Cheers!
#8
Putting things back how I found them...
#9
Thanks for the update.
Setting issue to "won't fix" rather than "fixed", since it is a feature request.