minor formatting

[ikiwiki.git] / doc / rcs / git / discussion.mdwn

diff --git a/doc/rcs/git/discussion.mdwn b/doc/rcs/git/discussion.mdwn
index e569786315ce08c749ca9dfa34b468f25fd938d7..92f630fc7170c915d3c83b071c5b0a5e9f524032 100644 (file)
--- a/doc/rcs/git/discussion.mdwn
+++ b/doc/rcs/git/discussion.mdwn
@@ -95,3 +95,9 @@ 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.
 > 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]]
 > 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
 > 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.