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.

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.