Q&A: using a local wiki to preview changes: an srcdir needed?

master
http://lj.rossia.org/users/imz/ 2009-05-13 19:44:27 -04:00 committed by Joey Hess
parent 815ed1edec
commit f11d67ebd0
1 changed files with 5 additions and 0 deletions

View File

@ -95,3 +95,8 @@ Does that mean that apache:apache should just own everything, and I should only
> Ikiwiki is designed so that you don't have to worry about this kind of permissions issue. > Ikiwiki is designed so that you don't have to worry about this kind of permissions issue.
> Instead you can just configure the ikiwiki.cgi, in the setup file, to be suid to your > Instead you can just configure the ikiwiki.cgi, in the setup file, to be suid to your
> user. Then there's no need to let the web server's user modify files at all. --[[Joey]] > user. Then there's no need to let the web server's user modify files at all. --[[Joey]]
## using a local wiki to preview changes: an srcdir needed?
I have read the hints about using a local wiki to preview changes, but I haven't understood: is it assumed that I should also have a separate "srcdir" for this local preview-wiki (as it is done for the main wiki site), or I could point the local ikiwiki's "srcdir" to the working dir? Can something bad happen if I do this? I guess no, because--as I see it--the reason to have 2 repos for the main site was only enabling pushing to it, so it's a peculiarity of git, and not a requirement for a clean functioning of ikiwiki.
Ok, probably, I have answered my question myself, but I'll let this comment stay here, if someone else will be tinking about the same issue. --Ivan Z.