Marc wrote:
> I used TortoiseSVN to create the repository. The repository is accessed by
> the clients using svn://svn.domain.com/trunk. I have an entry in dns for
> svn.domain.com.
>
> Now, I just created a SECOND website, and again set up a new repository on a
> separate directory on the hard drive, again using TortoiseSVN. I wanted to
> use svn://svn.domain2.com/trunk. However, when I point the client to THAT
> domain and trunk, I still get the FIRST repository I created.
>
> We want each website to have its own repository. I'm clearly doing
> something wrong, since it appears that only the one repository is
> recognized, no matter which repository I enter into the TortoiseSVN client.
>
> Can someone point me in the right direction?
You're probably running into the same basic limitation that FTP, POP3,
and a long list of other protols have with respect to supporting
multiple logical domains on a single IP - the protocol itself doesn't
have a method to specify which domain you're connecting to. (I'm sure
someone will also pipe up if I'm misinformed about this, too. <g>)
HTTPS has a similar issue in that while HTTP can specify which domain
you want to deal with, that information isn't available when
establishing the SSL handshake for an HTTPS connection, so more than one
website needing HTTPS access can't share an IP.
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.
-kgd
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 29 00:00:52 2006