On 2/4/07, Patrick R. Michaud <[EMAIL PROTECTED]> wrote: > On Sun, Feb 04, 2007 at 07:39:19AM -0500, The Editor wrote: > > >> >> pmwiki/ > > >> >> pmwiki.php (including pmwiki.php) > > >> >> "core"/ (or could call the barn =|:)> ) > > >> >> scripts/ > > >> >> wikilib.d/ > > >> >> guiedit/ > > >> >> cookbook/ (for farm wide recipes) > > >> >> skins/ (for farm wide skins) > > >> >> "field"/ (instead of data) > > >> >> writable/ (some better name--pages?) > > >> >> wiki.d/ > > >> >> uploads/ > > >> >> temp/ (for working files) > > >> >> nonwritable/ (some better name--system?) > > >> >> skins/ (from pub) > > >> >> config/ (css and php) > > >> >> cookbook/ (for field only recipes) > > > > Just thoughts. I know you'll come up with the best solution. I do > > think farms should be made as easy to set up and work with as > > possible. > > What part about the existing implementation is difficult to > work with now? What we have now is essentially: > > "pmwiki-core"/ > pmwiki.php > scripts/ > wikilib.d/ > cookbook/ > local/ > farmconfig.php > pub/ > guiedit/ > skins/ > > "field"/ > index.php > writable/ > wiki.d/ > temp/ > uploads/ > local/ # optional per-field config > cookbook/ # optional per-field cookbook > pub/ # optional per-field css/skins/other > > To me, this looks fairly close to what you've written above -- > where are the major differences? > > Pm
Actually nothing significant. This addresses my needs just fine. Looks great! Of course, shouldn't uploads be writable? Cheers, Dan PS. I do prefer writable to writable-private... _______________________________________________ pmwiki-users mailing list [email protected] http://www.pmichaud.com/mailman/listinfo/pmwiki-users
