Hello
Elgg installation takes one folder path (data folder path) and keeps both the cahe data (two subfilders of syste_cache and views_simplecache) in the same folder with other user uploaded content. Is there any way to separate the cache folder path from where other data is stored in the settings? I want to keep the data folder on a network location, while the cache data to be on the same machine that Elgg is running.
Any help is appreciated.
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by Raül Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
- Steve Clay@steve_clay
Steve Clay - 0 likes
- sistani@sistani
sistani - 0 likes
- Paweł Sroka@srokap
Paweł Sroka - 0 likes
- DhrupDeScoop@Dhrup2000
DhrupDeScoop - 0 likes
- Steve Clay@steve_clay
Steve Clay - 0 likes
You must log in to post replies.Sorry to say Elgg won't support that configuration, at least for now.
Thanks Steve. It would be good to consider it for a next release as it is easy to define a configurable variable for the cache data path, which may get a value other than the dataroot.
I'd like to see configurable cache paths in Elgg, but putting these caches in the same paths would be asking for trouble. But making sth like:
/dataroot
/different/path/cache/system_cache
/different/path/cache/simple_cache
Why not? We were working with Elgg on several instances and putting caches (system + simple) in local instance's tmp and dataroot shared via NFS is good way to save resources instead of synchronizing caches. Clearing caches was of course matter of deployment, we did it simply by calling REST API methods for each worker.
So I like idea of separating cache from data.
tasks do not involve more than 11 lines of php code that cater for data/ and cache/ locations;
some few more loc and parameterization of these can be done, quite easily..
i had presented this at Boston Elgg Conference, 2009 as part of ' Distributed Elgg, Conceptual Design & Directions ' -->
MYDOMAIN.COM:
/CONFIG.PHP:
$CONFIG->codeHost = 'http://www.CodeBase.Com/ELGG/';
$CONFIG->configHost = 'http://www.Config.Com/ELGG/';
$CONFIG->dataHost_A = 'http://www.DataHostA.com/ELGGDATA/';
$CONFIG->dataHost_B = 'http://www.DataHost.Bcom/ELGGDATA/';
...
$CONFIG->dataHost_Z = 'http://www.DataHostZ.com/ELGGDATA/';
...
$CONFIG->dataHost_9 = 'http://www.DataHost9.com/ELGGDATA/';
$CONFIG->dbHost_XXX = 'http://www.DataBaseXXX.com/MySQL/ELGG/';
BTW, I definitely see the value in separating data from temporary caches and welcome a ticket/patch to make this possible.