urosm
/
ikiwiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Comment on another possible solution to the use case.

master
http://www.cse.unsw.edu.au/~willu/ 2009-08-24 03:13:25 -04:00 committed by Joey Hess
parent 80ca685385
commit a27861c512
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/plugins/contrib/rsync/discussion.mdwn
View File

@ -25,3 +25,14 @@ As a proof of concept, I added an rsync post-commit hook after
ikiwiki's usual. It worked, just not for web edits, which is how
the wiki will be used. So I wrote this plugin to finish the job.
The wiki now lives on (1), and clicking "edit" just works.
> Just out of interest, why use `rsync` and not `git push`. i.e. a
> different setup to solve the same problem would be to run a
> normal ikiwiki setup on the universities server with its git
> repository available over ssh (same security setup your using
> for rsync should work for git over ssh). On the cgi-capable server,
> when it would rsync, make it git push. It would seem that git
> has enough information that it should be able to be more
> network efficient. It also means that corruption at one end
> wouldn't be propagated to the other end. -- [[Will]]