How to get master-master replication with Subversion?

Question

Seems like a simple problem:

• I have an SVN repo inside our firewall.
• I have an SVN repo outside our firewall.
• I have users inside, and outsi

Answer 1

http://wandisco.com/subversion/multisite/

Subversion MultiSite leverages WANdisco's unique replication technology to immediately synchronize Subversion repositories connected over a wide area network (WAN). Users at every location experience local area network (LAN) speed performance for both read and write operations. Subversion MultiSite also provides continuous hot backup and self-healing capabilities that automate disaster recovery, so that downtime is virtually eliminated.

Answer 2

If you are searching step by step explanation about master/slave replication using svnsync, please follow http://lasanthals.blogspot.com/2012/09/main-steps-of-configuring-svn_4.html

Answer 3

One of the features of the Enterprise Edition of VisualSVN Server is Multisite Repository Replication that does exactly what you are looking for.

The feature is based on VisualSVN Distributed File System (VDFS) technology which was designed to enable transparent Subversion repository replication across geographically distributed sites. Some of the notable features of VDFS:

• All distributed VDFS Subversion repositories are writable,
• VDFS enables transparent bidirectional data replication,
• VDFS supports replication authorization rules and advanced authentication mechanisms such as Integrated Windows Authentication (NTLM/Negotiate) with secure SSL/TLS encryption.
• All VDFS repositories contain the same dataset,
• Repository replication over WAN with VDFS is up to x10 faster than replication based on write-through proxy,
• VDFS configuration is done via a graphical interface without any complicated steps.

It's worth noting that VDFS follows the classic master-slave replication model which has significant advantages over master-master replication model because it's more suitable for replicating Subversion repositories with FSFS fs-type backend. VDFS technology is much more reliable than master-master replication solutions for SVN.

• VisualSVN Server | Multisite Repository Configuration,
• Comparing VDFS with master-master replication solutions.

Answer 4

The most seamless and scalable solution is the master/slave replication using svnsync that is described in the Subversion book: http://svnbook.red-bean.com/en/1.7/svn-book.html#svn.serverconfig.httpd.extra.writethruproxy

Answer 5

I'd recommend SVK or git-svn.

Both of these let you create an external mirror of your svn repository, and allow the external devs to make commits directly to the external mirror. You can then pull and push changes from this external mirror to your internal master repo.

git-svn would (I think) require the external developers to use git. I prefer it, but I'd be reluctant to push this on others.

SVK, however, allows the external developers to continue using svn. Since the internal repo is only accessible internally, an internal account or user would have to handle the periodic syncronization (a cron job would probably work).

Here's an extended howto on the SVK wiki: UsingSVKAsARepositoryMirroringSystem

Answer 6

One thing you could try is to replicate the repo at file level. I am using FolderShare (http://www.foldershare.com - runs on Windows and Mac) for a similar scenario, though I am replicating it only for backup purposes and have not tried to connect using SVN to the replica.