> This is also why PmWiki doesn't come with a web-based "installer" -- > it means that the files all get the wrong ownerships and permissions > if done that way.
but... would it be possible to have _another_ interface w/in the cookbook directory that could work this way? IE, something outside the pmwiki-core, that could call PM-wiki code to do some work there, but is not callable from the wiki-core itself? This is probably running down the same rabbit-hole as above. PmWiki is so much more secure than something like -- say, WordPress -- because of the lack of a web-based interface, yes? -the Other michael http://www.xradiograph.com Sent from John's Wireless BlackBerry StringCan iPhone On Mon, Jan 19, 2009 at 1:18 AM, Patrick R. Michaud <[email protected]> wrote: > On Sat, Jan 17, 2009 at 08:39:53PM +0100, jdd wrote: >> > Priority Checklist : >> >> one thing is probably very important: have some way to install major >> cookbooks from a drop down list or checkbox > > This isn't likely to happen (the drop-down list or checkbox part), > because we don't want the webserver to have write permission to > the cookbook/ directory. > > This is also why PmWiki doesn't come with a web-based "installer" -- > it means that the files all get the wrong ownerships and permissions > if done that way. > > Pm _______________________________________________ pmwiki-users mailing list [email protected] http://www.pmichaud.com/mailman/listinfo/pmwiki-users
