I have a svnserve subversion repository implemented by a Linux server on
my LAN which represents, from my perspective, the best solution for
version control of several projects. I primarily work on a Windows XP
laptop which I plug into my LAN when I'm in the office and also used to
access the same servers remotely using "poor man's VPN" - a single SSH
connection which forwards ports.
Hence when I'm in the office I can browse my repository:
svn://svnserver/
And when I connect remotely I need to use
svn://localhost/
While I accept that I could choose to connect to my server using a ssh
forward from my office as well as when connecting remotely, I'd prefer
to retain the performance advantage of a direct connection when I'm
connected to the LAN. The problem is that I might work on a patch both
while connected to the LAN and when remotely accessing my servers - but
when I try to commit from a checkout performed on my LAN remote commits
are directed towards an inaccessible server... and vice-versa. Is there
a straightforward solution? It seems I need some sort of indirection
that allows me to name a server differently depending upon available
connectivity. Is this the sort of thing that would be managed by
TortoiseSVN - or is the only solution to somehow arrange DNS to fudge
this for my needs?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Apr 11 13:18:14 2005