You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by bruce <be...@earthlink.net> on 2004/09/06 01:00:23 UTC
svn design/usage issue...
hi...
i'm strongly considering using svn.. and i'd like to get some
opinions/comments...
i'm considering an environment, where each function in an app will be
completely separate. i want to restrict the users working on the app to the
given function(s) that they have been assigned. as i understand svn, i
can/should be able to use apache/svn/mod_dav_svn and create a kind of
directory level access process, that will allow me to have users log into
svn, and restrict the dirs that the user has access to.
so far, so good.
the issue that i'm looking at has to do with the underlying working copies.
if i create the user access information on the server, the user then uses a
svn client to access the repository. on the client side, the user would
create a working dir/copy area. the user would then be able to
checkout/modify the files from the dirs that he has access to. this process
should allow the user to be able to access files from multiple dirs, and to
be able to check the files back in without accessing files in other areas.
have i missed anything...
i envision 400-500 separate dirs for the various apps. i'm also going to
have to periodically copy the different versions (once an app works!) into a
separate 'tag' dir.
comments/feedback/thoughts welcomed...
thanks...
-bruce
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn design/usage issue...
Posted by kf...@collab.net.
Peter Valdemar Mørch <sw...@sneakemail.com> writes:
> First off, please start a new thread by creating a new message to the
> list, and not by replying to an old message. When you "Reply", your
> email headers contain a line like this:
> > In-Reply-To: <10...@localhost.localdomain>
> So threaded mail readers will present them as part of an existing
> thread (under the one where Message-ID is equal to the string
> above). That lowers your chances of somebody replying to you.
Amen to that. By the way, this is
http://subversion.tigris.org/mailing-list-guidelines.html#fresh-post
(in case people want a convenient way to say the same thing in the
future).
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn design/usage issue...
Posted by Peter Valdemar Mørch <sw...@sneakemail.com>.
Hi Bruce,
First off, please start a new thread by creating a new message to the
list, and not by replying to an old message. When you "Reply", your
email headers contain a line like this:
> In-Reply-To: <10...@localhost.localdomain>
So threaded mail readers will present them as part of an existing thread
(under the one where Message-ID is equal to the string above). That
lowers your chances of somebody replying to you.
bruce bedouglas-at-earthlink.net |Lists| wrote:
> the issue that i'm looking at has to do with the underlying working copies.
> if i create the user access information on the server, the user then uses a
> svn client to access the repository. on the client side, the user would
> create a working dir/copy area. the user would then be able to
> checkout/modify the files from the dirs that he has access to. this process
> should allow the user to be able to access files from multiple dirs, and to
> be able to check the files back in without accessing files in other areas.
>
> have i missed anything...
No, that sounds right. Access to these local copies is determined by
standard operating system access rights. After check-out, these working
copies are just regular files. Any apache/mod_svn access rights will not
be honored at this point.
> i envision 400-500 separate dirs for the various apps.
Fine.
> i'm also going to
> have to periodically copy the different versions (once an app works!) into a
> separate 'tag' dir.
I recommend not doing a file-system copy (/bin/cp) but a copy in the
repository (svn cp). See the svn book about tags.
Peter
--
Peter Valdemar Mørch
http://www.morch.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org