Re: A patch to keep cache directory out of webroot

"Jonn Beames" <[email protected]> wrote in message 
news:[email protected]...
>
> (mostly just replacements of hardcoded var paths with calls to 
> xarCoreGetVarDirPath())
>
> This works, but I'm sure there are other ways to acheive the same goal. 
> What do people say?  All are welcome to participate in the process.

Don't want things to get mixed up - ie we are talking about a cache 
directory, and we are also talking about somewhere to store our 
config.system.php file  for xaraya install and xaraya boot ...

Two aspects I'm interested in in more detail and feel it needs to be thought 
out more generally in relation to many areas:

1. Could I ask what is planned to be stored in the /var path ? Or another 
way - what will the /var path be used for, or what do we want and not want 
it to be used for given it is used for many things at the moment? I'd like 
to see a clear and specific definition or listing of what will and won't be 
stored in the /var path.

2. Access or configuraiton options for:
a.  those that do and do not have access to directories outside of the 
webroot.
b. those that are on different operating systesm (Windows vs *nix)
c. dependent on 1. above - ie what is the /var path used for?
    (multisite boot?, cache? etc)

 I'll prefer to see something like:

/var directory - only minimal configs or vars to get Xaraya bootable or 
installed.
   This remains  where it is.

/site directory (configurable) on a per site basis
    (including one and only site if that is all there is - for consistency).
     - /configs or vars whatever you want to call it
     -/data - where site wide message templates, images :), workflow etc 
data goes
     - /themes (this is configurable now and can be setup to point to an 
existing theme dir or any other dir)

If any modules require extra or different web or not web accessible space, 
then they should handle that themselves as a configurable option, but using 
the above, for example, as a basis. Otherwise, I believe it becomes too 
complicated for initial setups.

xarCoreGetVarDirPath () should default to /var where it is, but also maybe a 
param:
xarCoreGetVarDirPath('site')...

.. just a few thoughts..

Jo



>  - Jonn