[dokuwiki] Re: more cleanup questions

On Sun, 26 Jun 2005 09:46:40 +0200
Matthias Grimm <matthiasgrimm@xxxxxxxxxxxxxxxxxxxxx> wrote:

> Did you rename 'cache' to 'meta' here?

No just left out the uninteresting parts ;-)

> That means that there must be another place for all those data that
> save temporarily information which can't be deleted without to disturb
> the currently running DokuWiki like locks, mlists, cookiesalts, etc.

I think locks should be different from the meta dir
 
> data/
> |-- changes.log
> |-- attic/
> |-- media/
> |-- pages/     <-- was data in your first mail, by acciddent?

jipp, a mistake

> |-- meta/
> |   |-- locks
> |   |-- mlists
> |   `-- _htcookiesalt

I'd like to keep this file in sync to the pages dir. See Stevens mail for the 
apropriate ASCII art. So we have the pages in the page dir, and possible meta 
information about the pages in the meta dir. This eta dir could be used by 
plugins and future feature enhancements to store any additional information on 
a page (eg. keywords)

> The cache for pages and media files could merged I think.
> 
> The contents of 'xhtml' seems to me as the cached pages and
> will be laced in the numbered directories, right?

correct, it's the cache of the rendered output. Using a different renderer 
would create a different cachefile. But we can do this with different 
extensions as well.

So we can merge them all.

> > If we add similar metadata later it could go into the same
> > dir using a different extension.
> 
> ...depending on how permanent the information is.

everything in meta should be as permanent as the corresponding page.

> I don't know which one is the best but I always would tend to more
> options if we got them at no costs. Why would you like to cut down
> your possibilities only to get a shorter configuration file? I don't
> know if this flexibility is ever needed but to built it in later would
> be hard. So if there are no very good reasons to have a hard coded
> directory structure, add the 'cachedir' and 'metadir' options.

The only reason is how simple it is to change. Eg. if I want to move the data 
directory out of the webserver root for security reasons. I would have to 
change 5 or more options instead of just one.

Hmm.. what about this: We use a single config option called $conf['savedir']. 
In init.php we then use something like this:

if(!$conf['datadir']) $conf['datadir'] = $conf['savedir'].'/pages';
if(!$conf['mediadir']) $conf['mediadir'] = $conf['savedir'].'/pages';
...

This way users could override single directories to their own likings but use a 
main savedir as default.

Andi

Other related posts: