Easy and simple guide to create a Subversion (SVN) server in Windows?

Hey

Ive been literally killing myself looking up guides but most are way outdated and/or complicated. I tried a few simply ones but they simply appear to be out of date.

Can someone point me on a easy way to set it up in Windows? Ive been trying to use (as a client) TortoiseSVN but I simply cant get it to work. So I need something simply and easy.....

Thanks a lot!

Do you need it to be SVN? Some time ago I've switched from CVS to Mercurial (even converting a repository we had, though only one branch) and I didn't regret. It is easier to maintain in my opinion. We've even run it for some time without a web server, it has some basic server built right in. We're smallish company (3-4 developers) and it works well for us.

However, you should understand the differences between the centralized (SVN) and distributed (Mercurial) solutions before you consider this, and even if you decide to go distributed, you might want to check out git as well.

You can't use TortoiseSVN to setup a SVN server. Its a client. You need to read the instructions on how to setup a server.

SVN is a client server program, you need a server and a client.

That said, SVN has lost popularity, with Mercurial and 'git' being more modern replacements.

There are three basic steps:

1) Install a Subversion server binary package. You can download one from http://subversion.apache.org/packages.html#windows. I usually use Win32Svn. The Collabnet one is interesting, though, in that it gives you additional administration (though it runs a Java web server, JBoss AS if I recall correctly, to host it.)

2) Create a Subversion database. See http://svnbook.red-bean.com/en/1.7/svn.reposadmin.create.html
(By the way, you did download and look over the Subversion PDF, right? http://svnbook.red-bean.com/)

3) Decide if you want to run with the built-in svnserver, or if you want to integrate into Apache. I always do the latter. Once again, the documentation comes to the rescue:
http://svnbook.red-bean.com/en/1.7/svn.serverconfig.choosing.html

But having said all of this, I have to agree with Martin and Pat that if this is for your own personal use, use git or mercurial.

I was told to install VisualSVN and to tell you the truth, I am very happy to see how easy it was to setup. Amazed

I can access it via HTTP but via svn:\\ Im having some issues. Anyone have any idea?

And for a Javascript project with few developers and access needed from the outside, I think a centralized system such as Subversion was the best idea. Plus, the outside party usually uses Subversion so...

The "svn" URL protocol requires that you be running a native SVN server (svnserver) network port. I don't bother to, since HTTP covers a lot more ground. Subversion itself doesn't care how it's accessed other than the fact that security for the svn native interface is defined in the SVN directory tree whereas the HTTP security is managed by your HTTP server.

The fad these days is for more "crowd-based" SCM, a la git and mercurial. These systems are handy in that you aren't dependent on a single central server. That can be convenient when you spend most of your time disconnected and/or the management of the project is uncertain, but SVN and even CVS still find a lot of use. There are also combined solutions where the user operates using a detached git archive that then syncs into a central SVN server. Handy if you do a lot of programming on the road.

First step: stick a Linux CD into the drive, and install.

There is no second step, you're done!

Since from this post, the application versions have changed so the following steps

should help.

Step-1: Install the wamp and Tortoise..[Anywhere]

Step-2: Install the subversion (http://sourceforge.net/projects/win32svn/) [c:/svn]

Step-3: Copy (mod_authz_svn.so and mod_dav_svn.so) from (c:\svn\bin) to

../wamp/bin/apache/Apache2.2.17/modules

Step-4: Copy (intl3_svn.dll and libdb48.dll) from (c:\svn\bin) to

../wamp/bin/apache/Apache2.2.17/bin

Step-5: Open httpd.conf and uncomment following lines
LoadModule dav_module modules/mod_dav.so
LoadModule dav_fs_module modules/mod_dav_fs.so

and add lines
LoadModule dav_svn_module modules/mod_dav_svn.so
LoadModule authz_svn_module modules/mod_authz_svn.so

It should look like this
-------------------
LoadModule dav_module modules/mod_dav.so
LoadModule dav_fs_module modules/mod_dav_fs.so
LoadModule dav_svn_module modules/mod_dav_svn.so
LoadModule authz_svn_module modules/mod_authz_svn.so
-------------------

Step-6: In httpd.conf add following lines before (Include "c:/wamp/alias/*")
<Location /svn>
DAV svn
SVNParentPath C:/svn_repository
</Location>

It should look like this
-------------------
<Location /svn>
DAV svn
SVNParentPath C:/svn_repository
</Location>
"c:/wamp/alias/*"
-------------------

Step-7: Open Windows Firewall and open/add port 3690

Step-8: Create directory i.e (C:\svn_repository\project)

Step-9: Right click "project" folder -> TortoiseSVN->Create repository here

Step-10: Restart wamp

Now you should be able to view svn on (http://localhost/svn/project)

Hope this helps !