I currently have a custom SVN/Apache installation set-up that uses
https://server/svn/projectname/trunk. It is only one repository and
each different "projectname" is just a folder under the one repository
located at https://server/svn/. Each time I look at VisualSVN, I
notice that the install requires that each folder at my "projectname"
level to be a repository. I have a lot of "projects" and do not want
to have to create repositories for each new one nor do I want to
create a "svn" repository so that my URLs would be
https://server/svn/svn/projectname/trunk...

Is there a way to have VisualSVN to work with just the base
Repository? If not, is there any plans to add this as a feature? If
there are no plans to add this feature, is it possible to "extract"
the authentication modules for use in a custom SVN/Apache
installation.

Julian Easterling

Reply via email to