> We have been running Subversion for a couple of months, everything has
> worked great. But that been with only a small number of users(15),
> groups(7) and projects(5), It hasn't been too much work administrating
> this, adding users to Apache and editing our authfile(groups and access
> to projects.)
> Now the interested has grown and we are thinking of using subversion for
> many more of our development projects.
We're using Subversion now for 200+ users, with around 30+ groups; we
hold a lot of parallel-teams structure that forces us to grant
permissions selectively on different paths of the tree.
We use mod_authz_svn, and until recently we've kept that hell manually
editing the files.
I'm finishing Subauthz now, just to scratch that particular itch.
My aim is to finish it soon, as least to a grade I can call it 1.0.
I know there are some other tools out there, though none of them seemed
to scratch me exactly as I needed... and it's been a great excuse to
play with Ruby and Rails for a while.
What it currently does:
* Manage multiple configuration-file pairs (htpasswd's & mod_svn_authz's).
* Create and modify users and passwords
* Create and modify groups of users
* Create paths and manage permissions on them
* Keep track of previous versions of files
What it lacks (and it will soon have):
* Manage multiple repositories per configuration ([repo:/path/] paths)
* A better look (no more than a wireframe, currently!)
* A way to access to the permissions-file history
What I'd like to add 'someday':
* Management of users in repos other than Apache's basic htpasswd files
* Embbedded security? (currently I use Apache to sec the access to the tool)
* Some SVN utilities (check repo's paths, create them if wanted, ...)
BTW; has anybody any suggestion about licensing?
I'm currently slightly towards GPL...
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sun Dec 25 00:40:00 2005