On Tue, Sep 28, 2010 at 7:28 AM, Ryan Schmidt <subversion-20...@ryandesign.com> wrote: > > On Sep 28, 2010, at 05:52, p4p...@web.de wrote: > >> well what should i do if i want 2 hosts, like a local/lan based visualsvn >> server AND a sourcefourge one ? >> seems, i can't have both, can i ? > > With regular Subversion, there must be one master repository. But there can > be slave servers that keep mirror copies of the master, to speed up read-only > operations. Write requests to the slave can be transparently proxied back to > the master. > > So you could use SourceForge for your master, and set up a local mirror on > your LAN to speed some things up. Read up on svnsync.
It's not clear at all to me that Sourceforge's Subversion setup would support this kind of "pass-through" service. The last time I used it, it was really configured to be the primary repository there, cut it's a very useful setup, better configured than many internal environments. This sort of thing is why Sourceforge now supports "git", to allow a more distributed approach, and it is effective. The clients and IDE tools are not as polished as those for subversion, but for distributed work at Sourceforge, it's the approach to use. It may even be compatible with git-svn gateways to allow your existing Subversion setups to remain in contact and pushing material to an upstream git branch, with a bit of tinkering: I've not personally tried that.
