[pmwiki-users] PmWiki work directory, re-revisited
christian.ridderstrom at gmail.com
christian.ridderstrom at gmail.com
Sun Feb 4 16:08:56 CST 2007
On Sun, 4 Feb 2007, Patrick R. Michaud wrote:
>>> "pmwiki-core"/
>>> pmwiki.php
>>> scripts/
>>> wikilib.d/
>>> cookbook/
>>> local/
>>> farmconfig.php
>>> pub/
>>> guiedit/
>>> skins/
cache/
>>>
>>> "field"/
>>> index.php
>>> writable/
>>> wiki.d/
>>> temp/
files/
>>> uploads/
>>> local/ # optional per-field config
>>> cookbook/ # optional per-field cookbook
>>> pub/ # optional per-field css/skins/other
> Yes, uploads are writable, but unlike wiki.d/ and temp/ the files in
> uploads/ need to be directly available to the webserver. And we also
> probably don't want "writable" to be appearing in the upload urls, as in
>
> .../pmwiki/writable/uploads/Group/somefile.zip
I'm personally fine with that, although I'd probably add a redirect
directive to .htaccess. However, if you do uploads/downloads etc via
pmwiki.php, don't we already have a complicated address?
> But the truth is that there's no one dimension that can neatly cover
> everything.
I reorganized things along two dimensions: private/public v.s. ro/rw.
> scripts/ farm private read-only core
> wikilib.d/ farm [1] read-only core
> local/ field private read-only local
> cookbook/ [2] private read-only local
> farmconfig.php farm private read-only local
> wiki.d/ field private read-write local
> temp.d/ field private read-write local
files/ field? private? read-write ?
> pub/guiedit farm public read-only core
> pmwiki.php farm public read-only core
> pub/css field public read-only local
> pub/skins [2] public read-only local
> uploads/ field public read-write local
pub/cache/ field? public read-write ?
> [1] It doesn't matter if wikilib.d/ is public or private.
> [2] Skins and cookbook recipes can be per-field or farm-wide.
>
> Anything listed "public" needs to have a reasonable url and an easy way
> for PmWiki to figure out the correct url or for an administrator to set
> it. (In general this is quite difficult already)
I added cache/ above. I don't think it has to have a reasonable URI.
I also added files/ which is used by a 'notify' script I've written for
monitoring changes to uploaded files. I don't know if there should be a
separate area where recipes can store persistent data.
Similarly, I could imagine a skin that allows users to modify the CSS
files. So maybe they would require to be stored in a public and read-write
area.
/C
--
Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
More information about the pmwiki-users
mailing list