[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Confused subversion?

From: markph <markph_at_mailcan.com>
Date: 2007-06-21 21:43:22 CEST

Thomas Harold wrote:
> A few clarification questions (I've forgotten the original thread and
> can't find it). Are you using a single repository where "projectname"
> is a top level folder within the repository or are you saying that each
> "projectname" are their own repositories?

The latter, each projectname is its own repository. For example:

http://svn.domainname/project1 points to /var/svn/project1/
http://svn.domainname/project2 points to /var/svn/project2/

Under each repository, I create the following:


Additionally...I created a /var/svn/_skel_ folder, which I use to import
into the newly created repository immediately after creation. I wrote a
very simple script 'mksvnrepo.sh' that creates the necessary folders,
repository and sets up my preferred skeleton.

Then...apache does the rest (having it set up properly now). User
permissions are specific to the svn.domainname.com virtual host, but are not
specific to each repository.

Thomas Harold wrote:
> I remember (vaguely) that there's a reason why, with a single
> repository, that you don't want it to be aliased(?) to the root folder
> in Apache. I think it has to do with files that Apache needs in the
> root folder which can't be done if the root folder points directly at a
> repository. Or maybe I'm confusing http access with WebDAV
> functionality (or is it one and the same)?

I do not know the answer to these questions.


View this message in context: http://www.nabble.com/Confused-subversion--tf579237.html#a11240163
Sent from the Subversion Users mailing list archive at Nabble.com.
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 21 21:43:23 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.