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

RE: Subversion and Project Environments (Dev / Test / Prod)

From: Scott Lawrence <slawrence_at_pingtel.com>
Date: 2004-05-31 13:52:34 CEST

On Sun, 2004-05-30 at 23:56, Brendan van Drempt wrote:
> Thanks for the feedback... I was thinking along the same lines as far as
> doing an export of your website files in the repository to the test / live
> websites so all the _svn folders and included files are not posted on the
> sctual site...

On apache, you can prevent the .svn metadata directories from being part
of the content like this:
# Some parts of the site are server resident working copies of
# a subversion repository. (They may be updated automatically by
# the /home/www/bin/server-working-copy script run from a
# commit-hook in the project.)
# This disallows access to the subversion metadata in those working
# copies.
<DirectoryMatch ".*/\.svn">
   Deny from all

> However how then do you know what revision your test / live
> site files are at and wether that is the most recent revision?

Use 'svnversion' to create a file in the web content that has the
version number in it.

In the Makefile that constructs my content, I have:
$(local_content)/.site_version: FORCE
        svnversion . > $@

> I don't want to have to copy up the entire site everytime I do an update.

I use rsync; the Makefile makes a local working copy, then as the last
step (run from a cgi script), it rsyncs that working copy to the
directory used as DocumentRoot.

  Scott Lawrence
  SIPfoundry server tools maintainer
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 31 13:53:14 2004

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.