On Mon, May 4, 2009 at 04:28, Irfan Sayed <irfu.sayed_at_gmail.com> wrote:
> Thanks for all reply.
> Here is our setup. we are using subversion 1.5.4 on linux fedora 10.
> we have total 3 sites. and what i need is all the sites shud able to write
> and send changes to other two sites.
> if there is a commit happned on one site then same changes shud reflect to
> other two sites.
> we are using apache (http) based subversion configuration
> will svnsync will work in this sitiuation??
> please advice
Yes, svnsync with a single master and the slave repositories doing the
write-through proxy for commits should work just fine.
> On Thu, Apr 30, 2009 at 9:36 PM, Les Mikesell <lesmikesell_at_gmail.com> wrote:
>> Andy Levy wrote:
>>> On Thu, Apr 30, 2009 at 11:24, Irfan Sayed <irfu.sayed_at_gmail.com> wrote:
>>>> multisite means every development site will have saperate subversion
>>>> and they will sync to each other every half an hour(lets say) to have
>>>> updated copy of source code.
>>> You don't need to purchase a separate product. As of 1.4, Subversion
>>> has the ability to sync changes to "slave" read-only repositories. As
>>> of 1.5, those slave repositories can be configured to proxy commits
>>> back tot he master.
>>> But before you do that, run some tests to see if you even need it.
>>> Subversion works very well over WANs.
>> Yes, I'd guess that most people using subversion check out working copies
>> in multiple locations with a single repository (and hopefully have a
>> reasonable backup scheme for the repository contents). It works very well
>> that way. Wandisco has some tricks to improve remote performance but if you
>> have reasonable connectivity you don't need it.
>> Les Mikesell
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-04 15:06:52 CEST