On 12/6/06, Rob Brenart <svn@oculardata.com> wrote:
> Andy Levy wrote:
> > On 12/5/06, Rob Brenart <svn@oculardata.com> wrote:
> >> Right now I have one repository I use, svn/src/ where I put all my
> >> different projects.
> >>
> >> I've recently started working with some outside contractors, and
> >> obviously want to give them access to the code they need. However, I
> >> don't want them to be able to download all of my source. At the least I
> >> don't want them to be able to modify it all.
> >>
> >> I'm using https for my access method.
> >>
> >> Basically, when I want to add a new user, I just run the htpasswd2 -m
> >> /path/to/.dav_svn.password username
> >>
> >> and give them a password, and they're in.
> >>
> >> So I have no idea where I'd go to limit things... advice?
> >
> > See
> > http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html#svn.serverconfig.httpd.authz.perdir
> >
> >
> Thanks, I read through that... and I get it all... turns out I was
> already using the right apache modules (I had set this up awhile ago and
> just had no recollection of setting those up, in part because it was so
> long ago and in part because Debian helped a lot)
>
> Anyway... I even understand the access files which I need to create,
> which is really the crux of the whole thing. But what I'm not seeing is
> where to put these files or what to call them. May seem trivial, and I'm
> sure it is... but I can't seem to find it in the docs.
>
Put 'em anywhere you like, named anything you like. Just so long as
Apache can access them, and other users who you don't want messing
with your security can't.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 6 12:49:03 2006