Hi !
I'm not sure I can reply to this bug, but it seems to be very related.
My goal is to use the admin plugin to manage local configuration,
directly in DokuWiki instead of editing /etc/dokuwiki/ files. There is
two reasons for that. First, it's obviously annoying to have an ssh
terminal and the browser, and switch between each other to apply
modified configuration. Then, the configuration page of DokuWiki also
lists plugin configurations, which are not in /etc/dokuwiki as far as I
know.
But in the default installation, dokuwiki expect the conf directory AND
the files to be writable. I can easily accept to give write access to
/etc/dokuwiki/local.php, but I don't like the idea to give all access to
www-data to the /etc/dokuwiki directory, since there is some apache stuff.
I tried to make hack. It works, but I can't test it well. I modified two
files in the config plugins. But I don't know how to post it as a patch
:) If you can explain me the procedure, I may try to upload it. By the
way, I can also post the two modified files...
I'm not sure it's a very good hack : the directory write access is not
verified before writing files, and backup files (which is the default
behavior) has been disabled, in order to prevent DokuWiki to create new
backup files in /etc/dokuwiki.
As a conclusion, I just want to ask you something : why don't you
organize the configuration symlinks on the other way ? Like acl.auth.php
and users.auth.php, let local.php and dokuwiki.php in their original
directory, www-data writable, and symlink them to the /etc/dokuwiki
directory. I'm not sure it follows Debian Guidelines, but it's always
the same thing with PHP software trying to deals with config files...
Hope this can help, and good work for packaging this great Wiki engine ;)
Adrien CLERC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
