[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Hooks

From: Ryan Schmidt <subversion-2008c_at_ryandesign.com>
Date: Sat, 18 Oct 2008 00:02:56 -0500

On Oct 17, 2008, at 18:36, Ravi Gehlot wrote:

> First of all, thanks for helping. This question was actually
> originated by my friend Eric Roberts. I also do not know how to fix
> this problem. But here is a scenario: Let's say that we have 2
> servers and both servers have different IPs under the same subnet
> which makes them members of the same network. Let's imply that we
> have SVN-Server installed in both server-machines and that one of
> them is a DEV server and the other is a TEST Server. How can I
> program my hook so that it commits across that same network from
> IP1 to IP2 meaning from Server 1 to Server 2? I could be wrong but
> it looks like hooks only work with the local protocol file:/// so
> how would I commit to a directory found in another machine instead
> of some local directory on the same machine?

That's a totally different question than you asked originally:

>> On Fri, Oct 17, 2008 at 5:15 PM, Ravi Gehlot <ravi_at_ravigehlot.net>
>> wrote:
>>> Can I use hooks to invoke an update when there is a commit on a
>>> repostiory
>>> when the code and repo are on differnt servers (same network)?

If what you really want is to have changes that are committed to one
repository automatically mirrored in a second repository, then the
correct way to set that up is to use svnsync. I'm sure you can find
info on it by Googling.

However, if both the master and the mirror are in the same subnet,
what's the benefit of having two identical repositories site by site
like that? I suppose it might be nice as part of a disaster recovery

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-18 07:03:18 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.