Multisite

[sureshkumar nandakumar <su...@gmail.com>]

Hi,

I hope currently we don’t have "Multisite" perception in Subversion.
In earlier we had a discussion with CollabNet and Windisco team.
Windisco team have a solution with Multisite concept. I am sure about
Subversion other support.

Can anyone suggest me, whether Multisite Concept is incorporated with
Subversion or not.
Our clients are working in different countries, it would be great if
we have Multisite solution.

Re: Multisite

[Thorsten Schöning <ts...@am-soft.de>]

Guten Tag sureshkumar nandakumar,
am Montag, 23. Januar 2012 um 12:45 schrieben Sie:

> Can you provide Software and installation/Setup guide documents?

It's all covered in the documentation:

http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html#svn.serverconfig.httpd.extra.writethruproxy

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail:Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/

Telefon.............030-2 1001-310
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hanover HRB 207 694 - Geschäftsführer: Andreas Muchow

Re: Multisite

[sureshkumar nandakumar <su...@gmail.com>]

Hi Ryan,

Thanks for your valuable suggestion..
Can you provide Software and installation/Setup guide documents?

It would be help to setup and meet my requirement.



On 1/23/12, Ryan Schmidt <su...@ryandesign.com> wrote:
> On Jan 22, 2012, at 23:42, sureshkumar nandakumar wrote:
>
>> I hope currently we don’t have "Multisite" perception in Subversion.
>> In earlier we had a discussion with CollabNet and Windisco team.
>> Windisco team have a solution with Multisite concept. I am sure about
>> Subversion other support.
>>
>> Can anyone suggest me, whether Multisite Concept is incorporated with
>> Subversion or not.
>> Our clients are working in different countries, it would be great if
>> we have Multisite solution.
>
> Subversion works on the idea of a single master repository. You can host it
> wherever you like -- perhaps the site where most of your developers are
> located, or the site with the fastest Internet connectivity -- but there is
> only one of them.
>
> You can additionally configure as many read-only slaves as you want. For
> example you could have a read-only slave at each site, other than the site
> where you have the master.
>
> The slaves can be configured to proxy write requests back to the master.
> Users at each site would then connect to the server at their site, and any
> read operations (like checking out, or looking at the log) would be fast.
> Write operations (like committing) will take a longer for those sites that
> have the slave copies and not the master.
>
> The concept of multiple master repositories is a special thing that the
> people at the WANdisco company have developed. You can pay them lots of
> money to use that software, and they will probably tell you many reasons why
> you need it. I recommend trying a normal Subversion setup, with a single
> master server (and if desired any number of slave servers) first, since the
> software to do that is free.
>
>
>
>

Re: Multisite

[Ryan Schmidt <su...@ryandesign.com>]

On Jan 22, 2012, at 23:42, sureshkumar nandakumar wrote:

> I hope currently we don’t have "Multisite" perception in Subversion.
> In earlier we had a discussion with CollabNet and Windisco team.
> Windisco team have a solution with Multisite concept. I am sure about
> Subversion other support.
> 
> Can anyone suggest me, whether Multisite Concept is incorporated with
> Subversion or not.
> Our clients are working in different countries, it would be great if
> we have Multisite solution.

Subversion works on the idea of a single master repository. You can host it wherever you like -- perhaps the site where most of your developers are located, or the site with the fastest Internet connectivity -- but there is only one of them.

You can additionally configure as many read-only slaves as you want. For example you could have a read-only slave at each site, other than the site where you have the master.

The slaves can be configured to proxy write requests back to the master. Users at each site would then connect to the server at their site, and any read operations (like checking out, or looking at the log) would be fast. Write operations (like committing) will take a longer for those sites that have the slave copies and not the master.

The concept of multiple master repositories is a special thing that the people at the WANdisco company have developed. You can pay them lots of money to use that software, and they will probably tell you many reasons why you need it. I recommend trying a normal Subversion setup, with a single master server (and if desired any number of slave servers) first, since the software to do that is free.