Patrick R. Michaud a écrit :
...except that the permissions to cookbook/ _aren't_ open,
even at install time.
when one install a cookbook, he have to open permissions, anyway... so
the very same people should be able to run a script? we don't change
PmWiki frequently :-)
may be the better
Em Domingo 24 Fevereiro 2008 19:17, Patrick R. Michaud escreveu:
- The configuration files are somewhat sensitive to the order in
which things happen -- some scripts have to be loaded early,
some late, some variables set early, others late, etc. So, any
sort of configuration utility has
Christophe David a écrit :
I'd like to second this. The recipe installation is by now very
programmer-style, adding a include line, setting some config variables,
writing some php in a new file...It's all not difficult but not user
friendly for non-programmer admins.
What about a
On Sun, Feb 24, 2008 at 07:19:48AM +, imoc wrote:
some thing with a cookbook list, with check boxes
when installing several cookbooks, the process is quite cumbersome and
annoying, and a such script should be quite simple (however I'm not
able do do it myself)
I'd like to
Patrick R. Michaud wrote:
A similar argument goes for storing parts of config.php into
a wiki page -- it means that someone who is able to modify
those pages somehow can start executing arbitrary scripts
on the server. There may be cases where this would be
okay, but in the general case I
Patrick R. Michaud a écrit :
The problem with using a web-based interface to install cookbook
recipes automatically is that it requires write permission to
the cookbook/ directory. That's a security risk we haven't
wanted to take yet.
This is especially an issue since basically anyone can
A similar argument goes for storing parts of config.php into
a wiki page -- it means that someone who is able to modify
those pages somehow can start executing arbitrary scripts
on the server. There may be cases where this would be
okay, but in the general case I think it's too big a
On Sun, Feb 24, 2008 at 11:19:19PM +0100, Christophe David wrote:
A similar argument goes for storing parts of config.php into
a wiki page -- it means that someone who is able to modify
those pages somehow can start executing arbitrary scripts
on the server. There may be cases where
On Sun, Feb 24, 2008 at 11:52:05AM -0500, DaveG wrote:
Patrick R. Michaud wrote:
A similar argument goes for storing parts of config.php into
a wiki page -- it means that someone who is able to modify
those pages somehow can start executing arbitrary scripts
on the server. There may be
could even be a sh script, to be done by the admin, not an online
administration tools.
- not everyone is using unix
- not everyone using unix has command-line access
WikiSh has most capabilities to do this currently except for the actual
download from pmwiki.org. It's a way to give unix
some thing with a cookbook list, with check boxes
when installing several cookbooks, the process is quite cumbersome and
annoying, and a such script should be quite simple (however I'm not
able do do it myself)
thanks
jdd
I'd like to second this. The recipe installation is by now very
11 matches
Mail list logo
