----- Original Message -----
From: "Ryan Schmidt" <subversion-2006Q1@ryandesign.com>
To: "MrBr @ GMail" <email@example.com>
Sent: Tuesday, March 21, 2006 5:44 AM
Subject: Re: Post comit hook website update
> On Mar 21, 2006, at 11:28, MrBr @ GMail wrote:
>> There is some problems using your idea.
>> 1) RSYNC is an Unix only program, it can't be used by Windows. Both of
>> my servers are windows based.
> Then perhaps that is a problem of your operating system and not of the
> idea. Perhaps if your operating system does not offer the facilities you
> require you should consider using a more-capable operating system.
It's not an operating system problem. Windows has rsync and SSH and even
Subversion tools available via the CygWin tool suite, at www.cygwin.com.
Running an SSH server on a Windows box is one of the safer ways to send
files to and from such as erver.
>> 2) The servers aren't on the same network so I have to use somthing like
>> FTP to transfer files.
> rsync works fine across wide-area networks, but if you prefer FTP, that's
> fine too. FTP is of course a wildly insecure protocol, so you'd want to
> use SFTP or FTP over SSH or something similar.
sftp is famous for mishandling symlinks, hardlinks, and not being able to
*delete* old files from the sftp recipient to exactly mirror contents. I
don't recommend it for mirroring sites.
>> I thought to use post commit script to send the file over the ftp, but
>> the post comit scrip is provided only with the folloing arguments "the
>> path to the repository, and the new revision number that was created"
>> (accoring to the manual).
>> Is there any way to know wich files were changed and to transfer them
>> maintaing the directory sructure?
> Sure you can determine what files were changed. That's what the svnlook
> program is for.
And if you use rsync, you don't have to worry about it. Rsync will do that
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Mar 21 13:35:46 2006