[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Checking out to remote location via WebDAV?

From: Ryan Schmidt <subversion-2008a_at_ryandesign.com>
Date: Mon, 7 Apr 2008 13:42:27 -0500

On Apr 7, 2008, at 10:12, Jensen, Adam wrote:

> I use SVN quite extensively to help me maintain code history for a
> PHP web application Iíve developed. Itís helped me greatly,
> especially in that I can easily keep track of whatís currently on
> the live server as opposed to what is still being developed.
>
> Unfortunately, moving those developments onto the live server once
> theyíre ready is a rather tedious process, one in which I tend to
> lose a lot of time. I was hoping someone here might be able to
> help me fix that.
>
> My SVN repository is currently just located on my local machine (at
> a file:/// URL); I check out a couple of working copies to
> different locations on my hard drive, one of which is the live
> ďreleaseĒ branch, and one of which is the trunk (for development).
> Whenever the trunk material is stable enough, I create a new
> release branch, switch the live working copy over to it, and upload
> the changes manually, one by one, via the WebDAV protocol (which is
> the only way I can access my live server). When Iíve changed a lot
> of files, this takes quite awhile.
>
> Iím wondering if anyone here knows of a way that I can checkout the
> contents of my local repository to a remote location via the WebDAV
> protocol, and similarly to update that remote location from my
> local machine? That way updating the live site would be dead
> simple, and accurate to boot.

No, that is not possible.

The way to do it is to ssh to the remote machine, and on the remote
machine, execute the "svn update" command in your production server's
working copy of your site. This requires you to have ssh access to
the remote machine, svn installed on the remote machine, and your
repository served on the Internet such that the production machine
can access it. It sounds like your setup doesn't meet these
requirements, so this solution won't work for you.

Another option would be rsync. Keep a local working copy of the
production site, switch/update it when you want, and then rsync it to
the production server. This requires you to have rsync (or ssh)
access to the production server.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-04-07 20:43:37 CEST

This is an archived mail posted to the Subversion Users mailing list.