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

RE: mod_dav_svn WC auto-update ... bug?

From: Dassi, Nasser <NDassi_at_141xm.com>
Date: 2005-01-17 21:12:34 CET

1 word: A-M-A-Z-I-N-G!

Yes, I merely skimmed that chapter as limited references from
Apache-Config section (ch6) referred back to it :o)

I just tried the post-commit hook script and it works like a charm! I
had no idea repositories had that built-in (with documentation to boot)!

Thank you, Ben, for all your help and patience.

Now that I have a clean Apache+SVN configuration, I guess it's time to
actually develop those client-paid projects, eh?!

Happy MLK :o)

Nasser Dassi
Sr. Technical Programmer
=========================================
E: ndassi@141xm.com
O: 212-297-8045
M: 917-747-6326
F: 212-297-8006
=========================================

-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]
Sent: Monday, January 17, 2005 2:56 PM
To: Dassi, Nasser
Cc: users@subversion.tigris.org
Subject: Re: mod_dav_svn WC auto-update ... bug?

On Jan 17, 2005, at 1:39 PM, Dassi, Nasser wrote:
>
> This is *exactly* what I want to accomplish.

Excellent. This problem is completely unrelated to autoversioning.

For example, I keep my personal website in a private repository on
red-bean.com. I check out a working copy of the website to my local
machine, make edits, then commit. When the commit enters the
repository, a post-commit hook script is automatically run which
executes 'svn update' on ~sussman/public_html/, which is a *different*
working copy. It just happens to be a working that's visible to the
world.

>
> My first confusion was that a PUT to a "network share" would actually
> update the filesystem target (just like mod_dav/mod_dav_fs) and then
> -- as second step -- update the SVN Repository. That, it seems, is
> not the case.

The "DAV svn" directive means: "make a DAV share available to the
world, but use a subversion repository as the filesystem." There is
*no* filesystem; the svn repository is just a database that can pose as
an imaginary filesystem to applications.

>
> Back to your "post-commit hook script"... Where would I accomplish
> this?
> Would I have to compile my own SVN build with extra commands? Or, is
> there an extra Apache module that supports this sort of functionality?
>

Read chapter 5, "hook scripts". It's a feature of any repository. It
has nothing to do with apache, or dav, or autoversioning. Hook scripts
work over any access method: file:///, svn://, etc.

> Pls keep in mind that the repositories and apache server and working
> copies are *all* on a remote server. I am looking to access them
> solely
> via WebDAV shares.
>

You want to access *everything* as DAV shares? All the repositories
and all the working copies? Why? That seems a bit strange to me.

> PS: The Apache configs were set to:
>
> Listen 81
> DocumentRoot "d:\htdocs\webdav\"
> <Location />
> DAV on
> {Auth stuff}
> </Location>
>

This exports the directory d:\htdocs\webdav as a normal DAV share.
Subversion isn't involved at all. It's just a coincidence that the
directory happens to contain .svn/ folders. Nobody's paying attention
to them.

> AND...
>
> Listen 81
> DocumentRoot "d:\htdocs\webdav\"
> <Location />
> DAV svn
> SVNPath "d:\repos\1"
> SVNAutoversioning on
> {Auth stuff}
> </Location>
>

This makes the *repository* available as an autoversioning DAV share.

So both of your configs here look fine to me.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 17 21:16:34 2005

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