Using SVN

Please do mind, the following “manual” is for use at my server. I’m willing to help you using SVN, but I use it for solitary use for school. If you are a programmer, and in need for Subversion services, I guess the Google adwords on the right will help you further

Before you go further, you will need to have credentials for this. You will need an Repository Path, Username and Password.

Installing SVN

You can install TortioseSVN from Tigris from this link. If you are unsure, you probably need the 32-bits version. After installation, SVN wants you to reboot. You are advised to do so.

Create a folder for the checkout

Because you need a folder to use, you need to create a folder for SVN-Usage. You probably want it in your school-documents (Something like “My Documents\School\SVN”. For this purpose, I’ve created an folder in my c:\, called repository.
Right click on some white stuff on the background, and use “Checkout”. Fill in the folder (in this case an testfolder in the repository)

In the next screen, it will ask for the credentials. You may use “test” with the password “test”. In the real version, you may use your own username and password.

And then, the checkout!

As you will notice, the revision is currently 55. This means that there are already 55 changes on the repository. You can imagine that if you check something in, this will only increase. Subversion seems to work already!

Ok, let’s do some editing in the file… At first, please mind that the “Repository” folder has an green mark on it:

Cool. Seems that everything is checked out, and nobody made changes to anything of the content. Let’s edit it. Enter the folder, and open the file. Edit something…

then save it, and close the editor. Almost immediately, the file (and folder!) will become red:

Cool! Seems that we did update the file You can check this new version in via an “commit”. Right click on the file (or folder, which is the same use), and select Commit:

Before an file should be committed, you probably want to add some remarks on it. What did you change, etc, etc. Enter something not fully useless in the “recent messages” box, because this can be seen in the repository. We’ll add something like “Testing an commit”.

After you edited the comment file, press OK. You will get your new revision code

Updating documents

If subversion works correctly, you will get warned with updates. I recommend you to check for newer files when you start at an file. You can use SVN Update (Right click on the map), and it will update your folder.

More to document:

Locking is to be discussed yet. For now, you are free to go