[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: svnserve/authz mod questions..

From: bruce <bedouglas_at_earthlink.net>
Date: 2006-10-05 17:59:37 CEST

hi walden,

thanks for the reply...

the files in the given folder(s) won't be copied between folders. users will
do the checkin/checkout process within the folder. the potential issue that
i'll have is that over time, the users who need to access the file will
change. in fact it could change over days...

the targeted system is to be used to parse information from 500-1000
schools. we want to restrict potential access to the underlying parsing
scripts/data as this forms a good chunk of the guts of our app. we
anticipate that over time, we'll have external developers touching these
files...

and there again, we haven't come across a good tool to automatically manage
the authz/svnserv files for the user/file access.

thanks

-----Original Message-----
From: Walden H. Leverich [mailto:WaldenL@techsoftinc.com]
Sent: Thursday, October 05, 2006 8:48 AM
To: users@subversion.tigris.org
Subject: RE: svnserve/authz mod questions..

Well, it seems you first need to answer the question of whether the 100s
of folders should be one repository or many. It's not always an easy
question to answer, but one obvious way to answer it is... Will you ever
want to copy between folders? If so, it's one repository.

Assuming it's one repository, authz will work just fine for allowing
specific users access to one part of the repository and not the other,
or read to one and read/write to another, etc. However, I'm not aware of
any nice front end to edit the authz file, but it's just a text file.

We've deployed svn in a situation where I both have many repositories,
and many projects in a common repository. We use a common (shared)
passwd and authz file for all the repositories, and right now we edit
them by hand. We are working on something more "friendly", but it's not
anywhere near ready yet.

-Walden

-- 
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@TechSoftInc.com
http://www.TechSoftInc.com
Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.) 
-----Original Message-----
From: bruce [mailto:bedouglas@earthlink.net] 
Sent: Wednesday, October 04, 2006 11:30 PM
To: users@subversion.tigris.org
Subject: svnserve/authz mod questions..
hi...
i'm looking at being able to do a project using subversion. the project
would have 100s of folders, with different files in the folders. i'd
like to be able to automatically manage the ability of users to be able
to access the information within the folders/files.
however, the tools that i've seen so far, (svnmgr/insurrection) don't
have the ability to manage user access at the folder/file level.
so... my question, should i look into modifying these tools to provide
folder/file level user access.. which could be a pain!!! or do i take
the easy way, and essentially allow each folder to become its' own
repository, which means i have 100s of little small repositories, but i
could place them all under the same dir...
in theory, i would/should/could potentially use the same svnserve/authz
file for the user access to the repositories as well...
thoughts/comments/etc...
thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Received on Thu Oct 5 18:03:41 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.