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

response

master
http://schmonz.livejournal.com/ 2009-08-24 04:20:31 -04:00 committed by Joey Hess
parent a27861c512
commit 8d504e6b3d
1 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -24,7 +24,7 @@ to automatically push any changed pages to (1).
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.
The wiki now lives on (1), and clicking "edit" just works. --[[schmonz]]
> 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
@ -36,3 +36,13 @@ The wiki now lives on (1), and clicking "edit" just works.
> network efficient. It also means that corruption at one end
> wouldn't be propagated to the other end. -- [[Will]]
>> Hey, that's a nice solution. (The site was in svn to begin with,
>> but it's in git now.) One advantage of my approach in this particular
>> case: server (1) doesn't have `git` installed, but does have `rsync`,
>> so (1)'s environment can remain completely untweaked other than the
>> SSH arrangement. I kind of like that all the sysadmin effort is
>> contained on one host.
>>
>> This plugin is definitely still useful for projects not able to use
>> a DVCS (of which I've got at least one other), and possibly for
>> other uses not yet imagined. ;-) --[[schmonz]]