On Saturday 28 August 2004 12:08, Ben Collins-Sussman wrote:
> On Fri, 2004-08-27 at 20:07, kfogel@collab.net wrote:
> > Mike Ladwig <mladwig@comcast.net> writes:
> > > 1. Use svnadmin dump and svndumpfilter to create a separate repository
> > > for staff A that has no branch B. The disadvantage is that if the
> > > decision is changed in the future, it will be hard to "remerge" the
> > > projects.
> > >
> > > 2. Setup for http access and use the http access controls (I found an
> > > email suggesting that I can limit branch access using webdav). The
> > > (huge) disadvantage here is that I will need to setup this new access
> > > method and retrain all the developers to use it.
> >
> > (2) is not so hard, and will do what you want. Note that it's not
> > just webdav, you may want to use mod_authz_svn.
> >
> > I don't see any other options besides the ones you mention.
>
> And what retraining is necessary? The svn client uses URLs. You're
> talking about switching from svn+ssh:// to http:// URLs. The user does
> a new checkout, and then everything is the same.
First of all, thanks to everyone who offered advice on this. I decided to go
the http direction and it hasn't been much of a hassle. The documentation is
excellent and everything has worked as expected. People will hopefully begin
migrating tomorrow.
I have one question remaining. I have set up everything and it all works,
except I want to prevent anyone from accessing the repository using http (I
have https working). Is there a way to do this?
Thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 1 21:57:11 2004