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

Re: Website Management / Open Questions

From: Ryan Schmidt <subversion-2006Q1_at_ryandesign.com>
Date: 2006-01-24 14:01:10 CET

On Jan 24, 2006, at 11:52, Georg Wittenburg wrote:

> 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?

You can use "svnlook dirs-changed -r $REV" to learn which directories
were changed by a revision, and act accordingly.

> - 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.

Is the repository on a different machine than the web server? Does
the repository server have spare disk space? If so, then I would keep
a complete working copy of the relevant subset of the repository on
the repository server and update it whenever a relevant commit
occurs. Then I would use rsync to synchronize this with the directory
on the web server. rsync will only send the changes over the network,
so it would be comparable to running svn up.

If, on the other hand, you only have a single server which is
handling both repository and web server, and this is the server with
the constrained disk space situation, then I don't know a solution.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 24 14:05:32 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.