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 server
> and they will sync to each other every half an hour(lets say) to have the
> 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.
> in your case , are you using single subversion server and all the
> developmenet sites are using same subversion servere remotely????
> if this is true they you might have facing lots of performance/effeciency
> On Thu, Apr 30, 2009 at 8:46 PM, Bob Archer <Bob.Archer_at_infor.com> wrote:
>> >our organisation is planning to use subversion multisite. I heard that
>> > WANDISCO is the >organisation which gives the subversion multisite product.
>> >has anybody used that wandisco product. any
>> > comments/opinion/issues/concerns?????
>> What do you mean by “multi-site”? We use svn “as-is” and it is accessed by
>> developers in 3 offices, (Tampa, Huston, Salt Lake City) without any extra
>> tools or products needed.
>> Perhaps I don’t know what you mean by “multi-site”.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-30 17:37:01 CEST