Paul Koning wrote:
>>>>>> "Flanakin" == Flanakin Michael C Ctr <Flanakin> writes:
>>>>>>
>
> Flanakin> You really need to refer to your web server docs for
> Flanakin> that. How you do it depends on the server software you're
> Flanakin> using and your server layout (i.e. is your web server your
> Flanakin> Svn server?).
>
> Sorry, I wasn't clear enough. The web server is Apache 2, and it has
> mod_dav_svn to serve up repository content. The same server (via a
> different part of its config) is also serving the "intranet" virtual
> host.
>
> paul
>
>
>
I believe this has been discussed on this board before as well. You can
create a post-commit hook that will call a separate command to update a
working copy somewhere. This will work if your commits are normally
small, and not high volume so that the update can finish before the next
commit triggers the next update. OR - you can create a cron job that
will regularly perform an svn export to any directory location you
choose. This has the advantage of not caring about whether you are in
the middle of a commit or not. So a high volume repository with a cron
job running every 5 minutes means that a change will take (at most) 4:59
before someone sees it on the live site.
Either way - you cannot (currently) host the site directly from the
repository. I doubt that it sits on anyone's radar to accomplish, either.
Hope that helps.
Regards,
Frank
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 27 19:04:28 2005