[pmwiki-users] PmWiki work directory, re-revisited
christian.ridderstrom at gmail.com
christian.ridderstrom at gmail.com
Sun Feb 4 17:07:26 CST 2007
On Sun, 4 Feb 2007, Patrick R. Michaud wrote:
> 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 ? [ See note ]
>
> pmwiki.php farm public read-only core
> pub/guiedit/ farm public read-only core
> pub/skins/ [2] public read-only local
> pub/css/ field public read-only local
>
> pub/cache/ field? public read-write local
> uploads/ field public read-write local
>
>> I added cache/ above. I don't think it has to have a reasonable URI.
>
> I think pub/cache/ is reasonable. Most publicly cached information
> tends to be images or css files where the url isn't commonly seen
> anyway.
Something you wrote a bit further down about how modifed CSS files could
be placed in cache made think: Why not call pub/cache/
pub/writeable/
Recipes that wish to create public files can then place them in that
directory, or preferably in sub-directories. I still wouldn't mind a
better/shorter word for writeable, but it is very clear to me at least.
Here's a thought. Would it help if we said that generally speaking
everything not in pub/ is private? The execptions that are also public
would be pmwiki.php and uploads/.
Then we say that only pub/writeable/ and down is public and writeable, and
we could have writeable/ for something that is private and writeable.
It's late, so this might all be mumbo jumbo.
>> 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.
>
> I think that files/ is essentially the same as temp.d/
Not really. It's contents shouldn't be deleted - you'd lose history
information. Anyway, I do agree with you about where to place it. The
directory should definetly go into something like
private-writeable/files/
or perhaps
private-writeable/recipes/files/
I missed writing that above. In reality, I've currently placed files/ in
wiki.d/files/
> I would think that skin-generated/modified CSS files should go into
> pub/cache/ . For example, this is exactly what the CSSInWikiPages
> recipe does.
This what made me think pub/cache/ should be called pub/writeable/...
instead.
G'night
/Christian
--
Christian Ridderström, +46-8-768 39 44 http://www.md.kth.se/~chr
More information about the pmwiki-users
mailing list