Thanks I will give this a try tomorrow.
Stilgar.
Main Topics
Browse All TopicsHi,
We want to install SVN Server to provide source control to our company. The server we want to install it on is a webserver running IIS so we want to avoid the need of installing Apache, and to be able to access the repositories using the svn:// protocol - no need for http:// access. All Windows installers I could find require to install Apache. Can you please advise on how to achieve the above?
Stilgar.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
OK, been there, done that. It was a bit trickey - you have to leave a space after the = sign, and escape the path with \". Just something to take a note of.
Also, I used the --listening-port option, and now I'm accessing my repo through svn://<server-ip>:port/my-
My only issue now is authentication - yes, the file formats are quite easy to grasp, but 2 questions on them:
1. After changed, do I need to restart the service, or is it checking those files upon update/login request?
2. I set a new user and password in conf/passwd, and then went to authz and added these lines:
[repository:/test-rep]
my_user = rw
* =
However, committs from my client are failing, saying autherization failed. How come it didn't even ask for my username/pwd (it does do that on another rep I have on a different server, through http).
Also, when do I use the repository: keyword, and when don't I?
Thanks for your help,
Stilgar.
Thanks, this did the trick. I also changed a setting there to prevent non-authenticated reads.
Now 2 last basic questions - sorry for making this last forever :)
1) When should I create a new repository and when should I just use sub-folders of the same repository? I'm thinking about separate projects with the same logins and groups, and several related projects. Would love to hear your opinion based on your experience.
2) svnadmin doesn't create the famous trunk/branch/tag folders - why is that? is it something I should create manually?
Stilgar.
Both of these are really up to how you want to implement your own structure,
1/ While this is entirely up to you and depends on the type of work you are doing, i would tend to suggest if you are able to seperate projects clearly then have seperate repositories for them, though you could group similar types of project within one repository if you wanted to. We tend to have a few repositories one for each of our main projects and a single one called small-dev-projects which we use to hold all our little bits that we dont feel warrant their own repository.
2/ the trunk/branch/tag folders have become the defacto standard as they are obvious and allow for most functionality that people require from a versioning system, this structure has nothing particularly to do with SVN itself. The short answer, yes you need to create this yourself.
There is nothing special about these folders, they are just folders. The contents of the tags folder is just copies of a folder in that repository at a particular revision.
The best advice i can give you besides a bit of research of what other people do is to setup a temporary repository and have a play, see how to do things. You are bound to mess things up a few times to start with so a test repository is always a good idea to play with things.
Kind Regards
mcuk_storm
Yes and no, you cant have a single root configuration file, but you can have a common passwd and authz file.
If you create a folder called conf in you root svn-repositories folder i.e. c:\svn-repositories\conf
In this folder place your existing passwd and authz files.
In you svnserve.conf file in each repository, have:
[general]
password-db = ..\..\conf\passwd
authz-db = ..\..\conf\authz
This will reference you global passwd and authz file so you will have the same user accounts for everyone.
In your authz file if you want everyone to have the same access to each repository you can just set a rule for [/]
which will apply those permissions to the root of each repository, if you want to reference a specific repository then use the format:
[repos-name:/]
Kind Regards,
mcuk_storm
Business Accounts
Answer for Membership
by: mcuk_stormPosted on 2008-05-24 at 13:13:40ID: 21640139
The subversion server installer at rg/project _packages. html
s/svn/trun k/notes/wi ndows- serv ice.txt rve.exe --service -r c:\svn-repositories" displayname= "Subversion Server" depend= Tcpip
min" create c:\svn-repositories\my-rep os
os\conf folder and edit authz and passwd files to setup the permissions, they are comments and fairly easy to understand.
http://subversion.tigris.o
does not include Apache, it includes the subversion modules that work with apache but not apache itself.
After installing the package you will need to set svnserve up to be a service, there are instructions for this at:
http://svn.collab.net/repo
Essentially you need to do:
mkdir c:\svn-repositories
sc create Subversion binpath= "c:\program files\subversion\bin\svnse
Then
net start Subversion
This sets up the subversion service and starts it, you will then need to create your repository
"c:\program files\subversion\bin\svnad
You now have a svn server running with a repository called my-repos available at svn://<server-ip>/my-repos
At this point the repository will be set to anonymous read access and auth write access but will not have any authentication setup, to set this up go into the c:\svn-repositories\my-rep
This should get you up and running,
mcuk_storm