You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Greg Thomas <th...@omc.bt.co.uk> on 2005/09/28 14:56:14 UTC

Moving servers

I'll hopefully be shortly moving my Apache based svn repository. Is
there a nice easy (e.g. via an HTTP 301 response code in place on the
old server) to tell the clients that it has permanently moved, or will
everyone have to 'svn switch' on all of their working copies?

TIA,

Greg
-- 
This post represents the views of the author and does
not necessarily accurately represent the views of BT.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Moving servers

Posted by Greg Thomas <th...@omc.bt.co.uk>.
On Wed, 28 Sep 2005 13:06:20 -0400, Frank Gruman
<fg...@verizon.net> wrote:

>How about making the new server the same name as the old server?

The trouble is the old server doesn't have a name, only an IP address
:-(

The new server has a name, so at least next time I'll be sorted!

Greg
-- 
This post represents the views of the author and does
not necessarily accurately represent the views of BT.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Moving servers

Posted by Frank Gruman <fg...@verizon.net>.
Ryan Schmidt wrote:
> On Sep 28, 2005, at 16:56, Greg Thomas wrote:
>
>> I'll hopefully be shortly moving my Apache based svn repository. Is
>> there a nice easy (e.g. via an HTTP 301 response code in place on the
>> old server) to tell the clients that it has permanently moved, or will
>> everyone have to 'svn switch' on all of their working copies?
>
> Subversion doesn't follow 301s (or 302s I think); you just end up 
> getting a cryptic error message. Everyone will have to switch their 
> working copies. Send everyone an email telling them to do so. :-)
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
How about making the new server the same name as the old server?  When 
you do the switch, change the server names so that DNS routes to the new 
server with the same concurrent name.

Then you don't have to trouble all of the users.  If the server only 
hosts Subversion and no other critical apps, this should be a relatively 
painless process.

Regards,
Frank

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Moving servers

Posted by Ryan Schmidt <su...@ryandesign.com>.
On Sep 28, 2005, at 16:56, Greg Thomas wrote:

> I'll hopefully be shortly moving my Apache based svn repository. Is
> there a nice easy (e.g. via an HTTP 301 response code in place on the
> old server) to tell the clients that it has permanently moved, or will
> everyone have to 'svn switch' on all of their working copies?

Subversion doesn't follow 301s (or 302s I think); you just end up  
getting a cryptic error message. Everyone will have to switch their  
working copies. Send everyone an email telling them to do so. :-)


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org