Without TortoiseSVN. Yep. Straight up command line.
This is a problem that’s plagued me for a while. I’ve tried to work out the kinks before, only to be frustrated by the various ways that you can affect the configuration on the windows host. I believe I’ve finally got the solution and I’m interested to find how many other folks run into this problem and have a different solution.
So without further ado, try the following:
- Download the windows version of the command line client.
- Download the putty suite of tools.
- Generate a new key pair on the remote unix server acting as the repo.
- Copy the private key from the remote server and convert it using puttygen.
- In your svn config file, include the following in the tunnel section (or where ever you’ve placed the key):
- Now use the svn+ssh syntax and list a url in the repo.
ssh=”C:/Program Files/PuTTY/plink.exe” -i “C:/Program Files/PuTTY/id_dsa.ppk”
You’re good to go.
For more information on generating ssh keys, check out this documentation.
UPDATE
Funny. Just posted this and pointed it out to a friend. He immediately responds with the following link:
http://agateau.wordpress.com/2007/07/03/windows-svnssh-and-the-subversion-command-line-client/
Same steps, lot more detail. I defer to the better example in this case. 😉