On Fri, Feb 7, 2014 at 3:11 PM, Bob Archer <Bob.Archer_at_amsi.com> wrote:
>> I've been using Apache to proide HTTP access to several different SVN
>> repository directories on a single server for about 10 years.
>> I'm moving everything to a new server and I was considering using SVNSERVE
>> in place of or in addition to Apache for access to the repositories.
>
> Sure... but I would question why you would want to do this. You are just making more work for yourself and I don't see any advantage to providing both protocols.
Available firewll ports for client environments. Many locked down
environments only permit HTTP/HTTPS outgoing, and do not open svnserve
ports or SSH ports for svn+ssh or svnserve ports. The same problem can
exist on the server side.
Now, me? I've often used "svn+ssh" for client write access, on a
designated alternative port such as 2022, with a locked down SSH
service restricted only to the "svn" user. I then provided "http"
access for read-only access to publicly available or non-authenticated
internal access.
> If you are looking for simpler management/upgrades I highly recommend Subversion Edge. It's free and make things simple to setup and manage.
>
>
>>
>> Is it possible to server multiple SVN repositories.. Where I mean completely
>> different SVN directories. not separate folders within a single SVN repo.
>> using SVNSERVE on a single server? If so, how?
>>
>> Also, is there any issue with running both SVNSERVE and Apache to provide
>> both SVN protocol and HTTP protocol access to the same SVN repos at the
>> same time?
>>
>> Thanks in advance,
>> Tom
Received on 2014-02-08 17:50:52 CET