diff options
| author | joey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071> | 2007-01-20 08:25:43 +0000 |
|---|---|---|
| committer | joey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071> | 2007-01-20 08:25:43 +0000 |
| commit | c504eca7198a365be1ea23aa3e19994ce718240c (patch) | |
| tree | ef468bb3c47de61d3e354701ddddecbec576d1ab /doc/bugs/ikiwiki.setup_require_blank_rcs_to_work_as_cgi_only.mdwn | |
| parent | 4e4b43898742c78fbd0e8d0281f2297ba8239a8e (diff) | |
| download | ikiwiki-c504eca7198a365be1ea23aa3e19994ce718240c.tar ikiwiki-c504eca7198a365be1ea23aa3e19994ce718240c.tar.gz | |
web commit by http://ethan.betacantrips.com/: hope this helps
Diffstat (limited to 'doc/bugs/ikiwiki.setup_require_blank_rcs_to_work_as_cgi_only.mdwn')
| -rw-r--r-- | doc/bugs/ikiwiki.setup_require_blank_rcs_to_work_as_cgi_only.mdwn | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/doc/bugs/ikiwiki.setup_require_blank_rcs_to_work_as_cgi_only.mdwn b/doc/bugs/ikiwiki.setup_require_blank_rcs_to_work_as_cgi_only.mdwn index a914bcc3e..bd8a82f6e 100644 --- a/doc/bugs/ikiwiki.setup_require_blank_rcs_to_work_as_cgi_only.mdwn +++ b/doc/bugs/ikiwiki.setup_require_blank_rcs_to_work_as_cgi_only.mdwn @@ -15,4 +15,9 @@ Should it be documented ? > without having to take care of the new files before svn commit-ting... > --hb (hugues) - +>> Hi. It sounds like you want a distributed RCS, where you can branch and commit changes locally and periodically +>> push changes back. What I do is use svk, which is a distributed RCS based on svn, edit using text editors on my +>> laptop, and periodically `svk push` up to the server, which triggers a rebuild on the server. I think [[Joey]] +>> works this way too, but I'm not sure. If you don't like editing pages "by hand" then maybe you should look at +>> [[git]] or [[mercurial]] -- they should theoretically allow you to run apache on a working copy which is itself +>> a branch of a working copy running on another machine, but I haven't used them so I don't know. --Ethan |