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

Re: Moving files to production after check-in

From: Bob Proulx <bob_at_proulx.com>
Date: 2005-08-12 23:56:51 CEST

Bryce Thornton wrote:
> I see in the FAQ that the common way to move repository check-ins to a
> live site is by making the live site a working copy. Once the
> check-in is complete a hook runs to do an svn update on the production
> site and all is well. Here's the URL to that FAQ entry:
> http://subversion.tigris.org/faq.html#website-auto-update

Yes. I do that all of the time.

> My problem is that our Subversion repository is not Internet
> accessible

Not internet accessable means..., what? You mention rsync. Does not
having internet access mean that you also do not have rsync access?

> and our hosting provider does not run Subversion. Thus, the
> solution in the FAQ won't work for us. Let me know if I'm wrong
> here.

I think you are correct in thinking you will need something at least
slightly different.

> Before using Subversion, I would simply use rsync to keep our test and
> production sites in sync. Is there a way to use rsync with the
> subversion repository in order to achieve the same thing? Anyone have
> a better way to do this?

I suggest that you do the same live update as in the FAQ to a staging
area. This would be an area that you control. Have the post-commit
script update this area the same as the FAQ example is talking about
to keep a website up to date. Then as the last step after the update
is complete I would rsync that tree (excluding the .svn files since
they are not needed) to the web site.

This will keep the web site automatically in sync with your updates
without needing to run subversion there. But it will need to be able
to synchronize files with your staging area such as with rsync.

It is possible and likely that at some point the network connection to
the web site will be very slow when an update is requested. This
means that several updates might stack up all at once. In order to
guard against this create a lock file for the update process so that
only one update process may run at a time. I usually do this to
prevent a meltdown of the server.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 12 23:59:01 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.