TortoiseSVN is a Subversion client, implemented as a windows shell extension. The coolest Interface to (Sub)Version Control.
Using TortoiseSVN Plugin for Eclipse 3.x you can acces to this incredible software inside Eclipse.
It is a really easy to use version control / source control client under a GPL license, i.e its free!
Since it’s not an integration for a specific IDE you can use it with whatever development tool you like.
If you’re not sure if TortoiseSVN is the best SCM solution for you, check out the SCM comparison.
Features of TortoiseSVN/Subversion
- Windows Shell (Explorer) integration. Can be used without any IDE.
- Icon overlays show immediately which files/folders need to be uploaded (committed) to the database.
- Easy to use dialogs for version control operations
- The UI is available in different languages.
- Global revision numbers. You can get old versions of your project and not just single files.
- Atomic transactions. Interrupted operations don’t affect the repository at all.
To use this plugin, you must download first Tortoise SVN client. You can download it here.
<!– google_ad_client = “pub-9315677404791393”; google_ad_width = 234; google_ad_height = 60; google_ad_format = “234x60_as”; google_ad_type = “text_image”; google_ad_channel =”3267834691″; google_color_border = “FFFFFF”; google_color_bg = “FFFFFF”; google_color_link = “0000FF”; google_color_url = “FFFFFF”; google_color_text = “000000”; //–>
Step1 : Created a fedora virutal machine clone.
I’ve been using subversion a lot recently – from using repositories with client development companies to installing it for clients – it seems to be the SVN month.
Here’s how I installed subversion on a machine with Fedora Core 4. For anyone learning or using Subversion, I highly recommend that you read the book.
You may already have subversion installed, if not, just run this:
# yum install subversion
# yum install mod_dav_svn
Then you’ll need to setup at least one repository. I’m going to need multiple repositories that I can use for different clients so I have a bit of extra admin work ahead of me. You can setup as many repositories as you need, but no matter what you’ll need at least one. Here create the folders…
# mkdir /svn
# mkdir /svn/repos
# mkdir /svn/users
# mkdir /svn/permissions
We need to give these folders the proper permissions
# chown -R apache.apache /svn
Then we need to tell subversion to make our first repository.
# svnadmin create /svn/repos/myproject
First, I need to setup a config file for svnserve.
# vi /svn/repos/conf/svnserve.conf
Then, look for variations of the following code and edit it as necessary. By default any anonymous user can access the code so to disable that you must include anon-access = none, just commenting the value out will not prevent anonymous access.
anon-access = none
password-db = passwdfile
realm = My SVN Repository
auth-access = write
The password-db is just a path to a file containing usernames and passwords. You’ll create this file especially for SVN. I create each file inside of the repository conf directory. So, save your changes and then we’ll create said user file.
# vi passwdfile
Enter in something like:
username = password
Anyway, you’ll need to start the svn server.
# svnserve -d –listen-port=3690
One side note – svnserve just runs and doesn’t have a way to stop besides killing the process. If you make changes to the svnserve.conf or user file you’ll need to restart svnserve.
# killall svnserve
Then, go ahead and test (best to do so on a different machine).
# svn co –username=myusername svn://mydomain/svn/repos/myproject
The system should then ask you for your password. Go ahead and run some tests.
Now, let’s setup apache.
Create a new apache include file that will hold our configurations (You may already have this is subversion was already installed).
# vi /etc/httpd/conf.d/subversion.conf
Now, this file will need to contain something like this to serve the repository through apache:
LoadModule dav_svn_module modules/mod_dav_svn.so
LoadModule authz_svn_module modules/mod_authz_svn.so
AuthName “Subversion Repository”
Now, this essentially tells apache to load the mods needed for svn. We need to create some files so that this config will work properly. The first is our htpasswd file which I named “/svn/users/svnpass”.
# htpasswd -cb /svn/users/svnpass username password
Next we need to create the svnauth file.
# vi /svn/permissions/svnauthz.conf
Inside we’ll place a list of users who have access to files:
username = rw
The “rw” states that this user has read/write access to the root repository /.
Restart your web server and you should be done.
service httpd reload
or you can use:
/usr/sbin/apachectl restart – this option outputs better error messages in case you’ve made some syntax mistakes.
Go to your repository and you should see subversion displaying the repo info.