Re: [viewvc-users] Using ViewVC for Secure Repository Viewing

"C. Michael Pilato" <[email protected]> Tue, 9 Jul 2013 00:58:44 -0700
Newsgroups gmane.comp.version-control.cvs.viewcvs.user
Message-ID <[email protected]>
On 07/08/2013 11:23 AM, Ayush Rawat wrote:
> Hi People,
>                I am doing a project for which I am supposed to make
> something like Google Code Project. For that Project Input is:
>
> 1. SVN repository (One Or More than that, Size is not an issue)
> 2. A username-password database.
> 3. An apache server.
>
> Output:
> Users having proper username password are able to see or checkout the
> repositories being viewed by them in their respective browser with user
> specific privileges.
>
> My Study says that ViewVC can help me with the viewing in respective
> browsers, Checkout (Maybe ...Not a big issue), and User privileges.
> And my question is, Can it help me with the functionality where
> authenticity for every user is being checked from the database ? Or a
> local file (Because I can have the database drop to that level)
>
> Any Help or Redirection would really be helpful :)

Ayush,

Ayush,

I think ViewVC will meet all your needs.  After all, several 
Google-Code-like systems (CloudForge, TeamForge, SourceForge, ...) use 
ViewVC for exactly the purposes you mention.

ViewVC does not have any authentication mechanism (identifying a user) 
built-in, but when installed behind the Apache HTTP Server, it will 
"piggyback" on that server, and use the authenticated username that 
Apache determines.

ViewVC's authorization support (validating what a user is and isn't 
allowed to see) is somewhat limited to the levels of support that 
Subversion's built-in access files deliver, but is designed to be 
(somewhat) modular in case you need to write your own authorization plugin.

------------------------------------------------------
http://viewvc.tigris.org/ds/viewMessage.do?dsForumId=4255&dsMessageId=3060055

To unsubscribe from this discussion, e-mail: [[email protected]].