On 4/28/07, Greg Cerveny <greg.cerveny@gmail.com> wrote:
<snip>
> Option 2
>
> On the svn box, checkout to a local folder and use a file mirroring
> utility to promote files to the production environment. This
> eliminates the risk of access to older code versions, but also inserts
> a third tool into the chain. Being windows and linux, the available
> solutions of rsync and unison are implemented poorly. A direct
> network connection (utilizing samba) has been determined to be too
> high of a security risk.
>
> Questions:
>
> Are there better tools for syncing files between windows / redhat than
> unison or rsync?
I use SyncBack freeware to keep my windows development box in sync
with my web host. It just uses native ftp, and has always worked
flawlessly for me once I figured out the many options, but I have an
environment where changes are getting replicated to multiple sites
from multiple sites - in other words, the source files are being
updated in multiple locations.
In other words, configuring SyncBack should be much simpler if you are
in control of a one-way flow direction of changes.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Apr 28 16:39:56 2007