yeah...
but not much. we're looking at creating a development environment for
various projects. (think sourceforge, but for our use/projects) as such, as
we define a given project, and set the project up, we'll need to create
it/manage it from a browser...
so, at a minimum we need to:
- create svn repos
-setup svn repos
-copy svn repos
-backup svn repos
-manage svn users (allow/disallow/enable/disable)
-manage/handle multiple projects/multiple users
-generate statistics for the svn repos/projects
-etc...
-----Original Message-----
From: Michael Hogsett [mailto:hogsett@csl.sri.com]
Sent: Friday, April 01, 2005 2:09 PM
To: bedouglas@earthlink.net
Cc: users@subversion.tigris.org
Subject: Re: intergration of svn via php
bruce wrote:
> right...
>
> for my thoughts, we're going to need the ability to allow users to create
> svn repos based on the projects that they create. we might restrict repos
> deletions to admins, etc.. so, for our needs we're going to need to create
> svnadmin/svn commands that incorporate 'user' information... yeah, i know,
> security issues!!!
Well it can be made safe with proper validation of the argument(s) (e.g.
dont allow stupid or dangerous things like importing /etc)
Have you thought about users having the ability to see/edit other users'
repos (since the web server is running as the web server UID, and not the
user's)? What about name space (e.g. two users wanting to create
"MyProject").
- Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Apr 2 01:02:43 2005