On Fri, Jul 30, 2010 at 08:32, STF SVN <lapsap7+svn_at_gmail.com> wrote:
> On Thu, Jul 29, 2010 at 22:40, David Weintraub <qazwart_at_gmail.com> wrote:
>>
>> The standard 'svn' protocol is faster, but it uses port 3690 by
>> default. It is very likely that your VPN will block traffic to this
>> port.
>
> Why so?
Sane network security policies block everything, especially
non-standard ports, by default. Since Subversion isn't a "common"
piece of software, it shouldn't be a surprise if this port is locked
down.
>> You can start svnserve on another port, and you can use ssh+svn
>> which allows for tunneling.
>>
>> I believe you can have a Subversion repository run using both the
>> svn:// protocol and the http:// protocol at the same time
>
> It's nice to hear so. But since I'm using Visual SVN server, I
> think I have to turn to that company to see if their product supports
> this "dual-port" function.
VisualSVN Server is just a distribution of Subversion bundled with
Apache, a nice installer, and an MMC snap-in for server
administration. Under the hood, it's still the same Subversion. It
should support multiple access methods just fine.
Received on 2010-07-30 14:51:20 CEST