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

Website Management / Open Questions

From: Georg Wittenburg <georg.wittenburg_at_gmx.net>
Date: 2006-01-24 11:52:48 CET

Hi all,

I know that the topic of managing a website using Subversion has come up
several times before, in
[http://subversion.tigris.org/faq.html#website-auto-update] and
[http://svn.haxx.se/users/archive-2004-10/0902.shtml] for example.

While I'd like to set things up just like described in the FAQ, there are two
problems with that:
- I'm running on a tight quota and don't want to waste the extra space
required for .svn directories.
- I don't have access to the httpd.conf and thus would have to add LOTS
of .htaccess files to disallow public access to the .svn directories.

Essentially, I'd like to have the benefits of doing a "svn up", but without
the .svn directories sticking around.

I've looked into using "svn export -f" in my post-commit hook as a way to only
export the actual content of my website without the version control
information. This has several problems:
- There are multiple projects in my repository. Yet I want the "svn export"
only to run, after a commit to the public_html project. I can retrieve this
information rather clumsily by saying something like "svn diff /path/to/repo
-r ($REV-1):$REV | grep public_html". Is there a better way?
- For efficiency, I only want to export those files that have been changed in
the last commit. However, afaik but there is not selective export.

Before I start thinking towards using the post-commit hook to generate a diff
and then calling patch to apply the changes to my website, I wanted to ask on
this list whether there is a more elegant way to do this.



Georg Wittenburg
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 24 11:54:21 2006

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.