Re: A patch to keep cache directory out of webroot

"David Dyess II" <[email protected]> wrote in message 
news:[email protected]...
> My opinion: leave multisites the way it is now, where you have site 
> specific folders in whatever 'xarsites' folder you configured it for.

>  No matter  what, you will somehow have to tell xaraya where the /var/ 
> folder is for each multisite.
<snip />

That's not so much of a problem for me, and is how the multisite module is 
currently setup. The real problem is what to do with the rest of the 
directories in the var directory which is growing and contain a mix of 
different types of data.

Certainly the /var directory should be able to be configured on a per site 
basis for multisites. For me, it is not the /var directory per se that is 
the real problem, but what is currently in it. Thus my original question 
about what should and shouldn't be in the /var directory.

As it is now, the output caching came in after the original mulisite module 
was written and happens to be located in the /var directory. Ideally, that 
cache directory should be able to be configured to the specific multisite's 
/var directory if necessary. Personally that would be an advantage for some 
multisites to have a separate cache directory to other multisites in the 
same install. It is one example of one type of data currently stored in the 
/var directory. There is now lots of different types of data in the var 
directory and that is posing a problem for moving around the var directory 
for multisites, and other situations.

<snip />

> Now, I realize that is just a tiny piece to a huge complex megastorm of 
> opinionated discomfort and agrevation.  But, I think somewhere compromise 
> is going to be required.  I'm not on the team, I'm just a luser, but 
> normally I think breathing before, during, and after 
> reading/reacting/responding to posts is probably a good idea sometimes :)

Well, I appreciate your input as you are using Xaraya and see where you 
needs are. The more feedback here the better and tis what i'm looking for.

Where i'm also going with this, is trying to work out a generalized storage 
mechanism for Xaraya files and you may be interested in this in that 
specifically atm, I'm was trying to work out where we can put image files as 
part of all this.
Category (data) images was a point in question. I'd like them out of the 
Xaraya core file directory tree - and that poses a few problems. However, 
whatever the answer for that i think it needs to be a solution that can be 
applied systematically in other areas of specific 'module required' 
writeable, web accessible and non-webaccessible space, outside the core 
directory tree, and either in our out of the webdoc root :). Also where we 
can maintain template overrides and have either (multi)site wide, or theme 
specific images - for example :)

> This is text, no emotion, no facial expression, no way to read between the 
> lines, sometimes it's hard to know how someone meant to say something.  I 
> think the patches newsgroup isn't such a good place for an extended thread 
> such as this one.

I agree with that and think the patch directory should be for patches only 
and any comment kept to the originating feature or bug report initiating the 
patch.
However, given the topic is here and not much response to my post elsewhere, 
I'll have a say here too :).

> Perhaps some private dev talk and brainstorming, then show us all what the 
> options are and discuss it publicly.
>
> Just my 1/100 Peso (darn budget cuts)
>
Thanks for the 1/100 Peso - appreciated :)  Any further input you may have 
on the subject I'm sure will also be appreciated.

We only have increments of 5 cents here as inflation blew away the 1 and 2 
cent pieces, so just my 5 cents again :)

Jo

> David.D