Hello, > On 17 January 2015 at 00:47, STF SVN <lapsap7+...@gmail.com> wrote: >> >> I know this mailing-list has nothing to do with VisualSVN server, but I >> really need some help. >> >> I need to set up SVN replication on the fly, aka write-through proxying, >> using VisualSVN server. I know the new version of VisualSVN server supports >> replication, but for technical reason, I'm still using old version 2.7.
You can't actually call write-through proxy as "replication on the fly". Its simple replication solution that runs `svnsync` on master server *after* each commit by post- hook scripts. Commits always go to master in write-through proxy, the "proxy" part is just about redirecting all writes to go to master server which then replicates them to slaves using `svnsync`. Another note: write-through proxy does not work with Integrated Windows Authentication (i.e. AD Single Sign-On). BTW, what are the technical reasons that require you to use VisualSVN Server 2.7 and don't allow it to be upgraded to 3.2? >> I have found some articles here and there, eg >> http://www.visualsvn.com/support/svnbook/reposadmin/maint/#svn.reposadmin.maint.replication >> and >> http://svnbook.red-bean.com/en/1.7/svn.serverconfig.httpd.html#svn.serverconfig.httpd.extra.writethruproxy >> etc etc and tried to follow them but failed. Maybe because those procedures >> are for Linux-based SVN server? And how much are those articles relevant to >> VisualSVN server, ie Windows-based SVN server? > > I've read > http://www.visualsvn.com/support/svnbook/reposadmin/maint/#svn.reposadmin.maint.replication > several times, but I have a doubt. Does it apply totally? Can I consider > VisualSVN Server like a *generic* Apache HTTP server? Or VisualSVN Server > has some special modification to Apache such that something wouldn't work? It applies but not totally because sample hook scripts specified in SVNBook work on *nix Shell only, so they have to be adjusted to work on Windows. Here is a sample post-commit hook that will work on Windows (its a batch script (.bat)) [[ "C:\Program Files (x86)\VisualSVN Server\bin\svnsync.exe" sync https://SLAVE/svn/repo file:///C:\Repositories\MASTER exit 0 ]] and post-revprop-change hook [[ "C:\Program Files (x86)\VisualSVN Server\bin\svnsync.exe" copy-revprops https://SLAVE/svn/repo file:///C:\Repositories\MASTER exit 0 ]] > I have also found this article: > http://www.cardinalpath.com/how-to-use-svnsync-to-create-a-mirror-backup-of-your-subversion-repository/ > but it didn’t talk about putting the SVNMasterURI variable inside HTTPD > config on the slave server. And as a matter of fact, I’ve gone through this > procedure but I cannot commit to the slave server! The article is not about write-through proxy, it's about creating a backup repository that's always up-to-date. That's why this article doesn't cover the proxy part (i.e. SVNMaserURI config on slave server). -- With best regards, Pavel Lyalyakin VisualSVN Team
