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

Re: sharing a checked-out project amongst users

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: 2007-11-09 16:38:30 CET

Michael Stillwell wrote:
> Is there a recommended way to do this? We don't really want to use
> rsync, cp, etc. to copy a working copy into the live web
> directory--this would seem to introduce a lot of unnecessary work and
> complexity since "svn up" does 95% of what we want.

Personally I think using rsync from a staging directory is worth the
effort and makes it easy to push to any number of servers as your site
grows. Rsync also replaces files the 'right' way by copying under a
temporary name, then renaming to replace the old one atomically, at
least on filesystems with unix-like semantics. I'm not sure if this
also applies to svn updates. In any case, the clean way to permit
multiple users to do something is to run the actual command via ssh
using keys to control who can do it. That is, even if you do use an svn
update command on the server(s) to pull content, use a script that can
run the command on multiple servers.

> And updating via
> a commit hook (i.e. completely automated) is a bit fussy and
> inflexible for the projects we work on.

Agreed - you probably don't want to push everything you commit to
production unless you can embed some serious QA testing as part of the

   Les Mikesell
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 9 16:38:09 2007

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.