SVN help : multiple repo configuration

["Neson Maxmelbin (RBEI/EMT5)" <Ma...@in.bosch.com>]

Hello ,

I have setup SVN 1.6 with Apache 2.2 on a Windows Server 2003 R2 virtual server.

I want to setup two repositories , so I have configured two <Location .... > sections in the httpd.conf and it seems to work.
My Question is , is this a good practice or will this cause some errors/issues?

The reason I want to do this is that the server will serve multiple departments . Each repositories will have multiple projects.

Thanks for your answers.

Thanks and Regards
Maxmelbin Neson

RE: SVN help : multiple repo configuration

[Giulio Troccoli <Gi...@uk.linedata.com>]

>


Linedata Limited
Registered Office: 85 Gracechurch St., London, EC3V 0AA
Registered in England and Wales No 3475006 VAT Reg No 710 3140 03

-----Original Message-----


> From: Cooke, Mark [mailto:mark.cooke@siemens.com]
> Sent: 11 November 2010 12:50
> To: users@subversion.apache.org
> Cc: Neson Maxmelbin (RBEI/EMT5)
> Subject: RE: SVN help : multiple repo configuration
>
> > From: Neson Maxmelbin (RBEI/EMT5)
> > Sent: 11 November 2010 12:23
> > Subject: SVN help : multiple repo configuration
> >
> > Hello ,
> >
> > I have setup SVN 1.6 with Apache 2.2 on a Windows Server 2003
> > R2 virtual server.
> >
> > I want to setup two repositories , so I have configured two
> <Location
> > .... > sections in the httpd.conf and it seems to work.
> > My Question is , is this a good practice or will this cause some
> > errors/issues?
> >
> > The reason I want to do this is that the server will serve multiple
> > departments . Each repositories will have multiple projects.
> >
> That is how we have configured our system, with
> SVNParentPaths under each <Location> so that new repositories
> appear in the department's list automagically.  We still need
> to manually create new repositories but that's not a heavy
> admin burden.
>
> I've not had any problems yet and hope that this will help to
> isolate any future problems to a minimum of projects...

We don't use the SVNParentPath but each repositories, although they are all in the same place, have its own <Location> with SVNPath. We found this allows for better configuration, especially as they all have slightly different requirements.

We've been using it for 5 years, without any problem.

G

RE: SVN help : multiple repo configuration

["Cooke, Mark" <ma...@siemens.com>]

> From: Neson Maxmelbin (RBEI/EMT5) 
> Sent: 11 November 2010 12:23
> Subject: SVN help : multiple repo configuration
> 
> Hello ,
>  
> I have setup SVN 1.6 with Apache 2.2 on a Windows Server 2003 
> R2 virtual server.
>  
> I want to setup two repositories , so I have configured two 
> <Location .... > sections in the httpd.conf and it seems to work.
> My Question is , is this a good practice or will this cause 
> some errors/issues?
>  
> The reason I want to do this is that the server will serve 
> multiple departments . Each repositories will have multiple projects.
>  
That is how we have configured our system, with SVNParentPaths under
each <Location> so that new repositories appear in the department's list
automagically.  We still need to manually create new repositories but
that's not a heavy admin burden.

I've not had any problems yet and hope that this will help to isolate
any future problems to a minimum of projects...

~ mark c

Re: SVN help : multiple repo configuration

[Ryan Schmidt <su...@ryandesign.com>]

On Nov 11, 2010, at 06:23, Neson Maxmelbin (RBEI/EMT5) wrote:

> I want to setup two repositories , so I have configured two <Location …. > sections in the httpd.conf and it seems to work.
> My Question is , is this a good practice or will this cause some errors/issues?
>  
> The reason I want to do this is that the server will serve multiple departments . Each repositories will have multiple projects.

Sure, you can do that, that's fine.

Or you can write a single <Location> block that has an SVNParentPath directive (instead of multiple <Location> blocks with SVNPath directives). If the repositories have similar configurations, then this lets you have as many repositories as you want without ever adding more lines to your httpd.conf.