On Aug 22, 2008, at 11:02, David Weintraub wrote:
> One of my big complaints with viewvc is that it accesses the
> repository directly. I can see why (speed), but it does cause problems
> when you have the svn server process run as a different user from your
> viewvc process. Plus, it means you have to have "viewvc" run on the
> same system as your repository. Our standard development webserver is
> one system and our Subversion repository was on another system. I
> would have loved viewvc run on ur development webserver, but had to
> run it from our Subversion repository because of this.
>
> Fortunately, since we use http:// on our Subversion repository, this
> wasn't too much of a problem for us.
>
> Here's a possible solution:
>
> Run a cronjob to
>
> 1). Do a hotcopy of your subversion repository
> 2). Do a chown to the viewvc user
> 3). Do an rsync to a copy of your Subversion repository on your server
> where viewvc runs.
>
> This means that your commit results won't show up on viewvc until the
> next sync, but if you run the cronjob every ten minutes or so, it
> might be good enough.
If you're going to do that, you may as well use svnsync in the post-
commit hook to get the copy of the repository on the viewvc server to
be always up to date.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-22 18:25:53 CEST