Thanks for the replies Mark and Ryan. Here is the summary:
1. We've setup SVN server for our entire department, which is an
umbrella for 5 departments.
2. Within the main department that will use SVN (UIS), we need several
repositories for: mainframe and Lotus Notes archiving from our change
management process, internal unit usage (processes, policies, etc), and
new systems / projects.
3. There is concern about the archiving repositories especially because
the minimal size of Lotus Notes database templates is 500k with several
templates being archived every day, which are binary.
4. Our SVN server is running 32-bit RHEL 4 and hasn't been configured
for large file support; files are limited to 2 GB. All repositories are
created using the file system.
The largest, real concern is hitting the 2 GB limit. Other than that,
there are the typical concerns of storing everything in a single
1. What happens when an analyst ends up checking out the entire thing?
(They just learn not to do it again, IMHO)
2. What issues are there with backing up large repositories?
3. What administration changes are needed for very large repositories?
When do performance issues arise? What can be done to keep SVN
I apologize if this seems blatantly obvious to some, however, I was
"elected" to be the SVN administrator simply because I was the developer
with the most experience using it. Other than this mail list, I
scarcely find commentary about these issues anywhere else.
Andrew R Feller, Analyst
University Information Systems
Louisiana State University
From: Mark W. Shead [mailto:email@example.com]
Sent: Tuesday, April 17, 2007 2:52 PM
To: Andrew R Feller
Subject: Re: Organizing repositories into hierarchy of directories at
Apache's SVN root
On Apr 17, 2007, at 2:25 PM, Andrew R Feller wrote:
> Recently, my company has been looking to reorganize our
> repositories such that the Subversion root level pointed to by
> Apache's SVNParentPath contains repositories and directories of
> repositories. From the documentation provided by the SVN book
> (http://svnbook.red-bean.com/en/1.1/ch06s04.html), it seems I will
> have to setup multiple <Location> entities; one for each directory
> that is organized to hold repositories. However, as we have
> processes in place for automatic generation of repositories, I need
> to ensure whether this is the only viable option or not.
It sounds like you want to do something like:
Is that what you are thinking of doing?
I would suggest either creating one big repository at the top level
or creating separate top level repositories. If you want to have
directories and repositories both at http://www.yoursite.edu/ I think
you are going to run into problems. It might be possible with some
fancy configuration, but it is unlikely to be worth the time you'd
spend maintaining it.
Don't forget that you can create folders within a repository. You
don't have to use trunk, tags, branches at the top level of a repo.
Are you trying to mirror some organizational structure or something?
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Apr 18 15:26:52 2007