To use TortoiseSVN (or any other Subversion client), you need a place where your
repositories are located. You can either store your repositories locally and access
them using the
file:// protocol or you can place them on a
server and access them with the
The two server protocols can also be encrypted.
or you can use
svn:// with SASL.
If you are using a public hosting service such as Google Code or your server has already been setup by someone else then there is nothing else you need to do. Move along to Chapter 4, Daily Use Guide.
If you don't have a server and you work alone, or if you are just evaluating Subversion and TortoiseSVN in isolation, then local repositories are probably your best choice. Just create a repository on your own PC as described earlier in Chapter 3, The Repository. You can skip the rest of this chapter and go directly to Chapter 4, Daily Use Guide to find out how to start using it.
If you were thinking about setting up a multi-user repository on a network share, think again. Read the section called “Accessing a Repository on a Network Share” to find out why we think this is a bad idea. Setting up a server is not as hard as it sounds, and will give you better reliability and probably speed too.
More detailed information on the Subversion server options, and how to choose the best architecture for your situation, can be found in the Subversion book under Server Configuration .
In the early days of Subversion, setting up a server required a good understanding of server configuration and in previous versions of this manual we included detailed descriptions of how to set up a server. Since then things have become easier as there are now several pre-packaged server installers available which guide you through the setup and configuration process. These links are for some of the installers we know about:
You can always find the latest links on the Subversion website.
You can find further How To guides on the TortoiseSVN website.