aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/ikiwiki.setup_require_blank_rcs_to_work_as_cgi_only.mdwn
blob: bd8a82f6ee60c80e0c12de8256b357cb4ae00e1f (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
I have a mobile setup of ikiwiki.

* On my server, I set up an ikiwiki + svn
* On my laptop, I did a check out of the svn and used it as the src of a local ikiwiki (local apache server)

I wanted to be able to change my wiki off line with cgi only, and just commit as I come back online.

During the laptop setup, I think that the setup was confused by the fact that my src directory is a versionned one.
I had to setup explicitely rcs => "" to force it to work the way I wanted.

Should it be documented ?

> after some tests, the main trouble with this setup is that it won't make the "svn add" for the new files.
> I wonder what should be the setup if I want to use ikiwiki off line on the laptop and then commit back the changes, 
> 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