I didn't see the original email, but I just setup a system where the
URLs are:
http://repo.company.com/
and
https://repo.company.com/
A domain wide SSL certificate will allow this without problem.
On an interesting side note, this system is run load balanced across
several HTTP servers with FSFS repos on a Red Hat Cluster System GFS
filesystem.
Working like a charm so far!
On Sep 29, 2006, at 10:07 AM, Kenneth Porter wrote:
> --On Thursday, September 28, 2006 6:00 PM -0400 Kris Deugau
> <kdeugau@vianet.ca> wrote:
>
>> You'll have to do one of:
>>
>> -> Set up each site on separate IPs, so that services like SVN can
>> properly match access to different sites to the matching back-end
>> data.
>> -> Switch to HTTP access (please note, not HTTPS, as that will
>> just dump
>> you back where you started). This is probably the best long-term
>> option.
>> -> Rethink your repository structures so that you embed the
>> repository
>> name in the svn:// url somewhere after the domain name part.
>
> Or run separate servers on different ports. (This would also
> address the HTTPS limitation.) The downside is that you have to
> explicitly specify the port in the URL.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 2 06:13:24 2006