Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
subversion [2011/01/03 22:35]
stiber Added tags
subversion [2013/08/22 02:22] (current)
stiber A little cleanup and a little more information.
Line 7: Line 7:
 ===The Repository=== ===The Repository===
  
-There are two aspects to repository setup: svn and ssh. I won't go much into svn setup itself, other than to indicate that I'm assuming that the repository directory is ''​~/​svn'',​ with configuration files in ''​~/​.subversion''​. You'll need to read up on svn enough to set up the repository (or else, someone will need to edit a tutorial here).+There are two aspects to repository setup: svn and ssh. I won't go much into svn setup itself, other than to indicate that I'm assuming that the repository directory ​(on home, for example) ​is ''​~/​svn'',​ with configuration files in ''​~/​.subversion'' ​(on the user machines). You'll need to read up on svn enough to set up the repository (or else, someone will need to edit a tutorial here). You'll also need to set up a shared account (either course or departmental) for your project(s) using the UW IT [[https://​www.washington.edu/​computing/​forms/​shared/​| Shared UW NetID Account Request Form]].
  
 The ssh setup is a neat trick. The idea is that you can attach, to each public key, a command that is run when a user logs in with that key. This allows for secure connections,​ authentication,​ restriction of access on a per-user basis, and the ability for single users to be able to connect in multiple ways to the same account (simply by using different keys). The basic idea is to use the extended syntax of the ''​~/​.ssh/​authorized_keys''​ file: The ssh setup is a neat trick. The idea is that you can attach, to each public key, a command that is run when a user logs in with that key. This allows for secure connections,​ authentication,​ restriction of access on a per-user basis, and the ability for single users to be able to connect in multiple ways to the same account (simply by using different keys). The basic idea is to use the extended syntax of the ''​~/​.ssh/​authorized_keys''​ file:
Line 40: Line 40:
  
 <​code>​ <​code>​
-homer = /​usr/​bin/​ssh -p 22 -q -l biocomp ​-i /​path/​to/​home/​.ssh/​id_rsa-svn+homer = /​usr/​bin/​ssh -p 22 -q -l [repository-UID] ​-i /​path/​to/​home/​.ssh/​id_rsa-svn
 </​code>​ </​code>​
  
-This creates a "​svn+homer"​ tunnel scheme (where you need to change "/​path/​to/​home/​.ssh/​id_rsa-svn"​ to be the full path to your private key). You can change "​homer"​ to whatever you'd like the tunnel scheme to be named. For configuring other clients, see [[http://​wiki.site5.com/​SVN/​Subversion_(SVN)_Setup_Guide]] near the bottom for clues. From the command line, you can try+This creates a "​svn+homer"​ tunnel scheme (where you need to change "/​path/​to/​home/​.ssh/​id_rsa-svn"​ to be the full path to your private key and "​[repository-UID]"​ to the repository account user ID on the server). You can change "​homer"​ to whatever you'd like the tunnel scheme to be named. For configuring other clients, see [[http://​wiki.site5.com/​SVN/​Subversion_(SVN)_Setup_Guide]] near the bottom for clues. From the command line, you can try
  
 <​code>​ <​code>​
Line 50: Line 50:
  
 to list the ''​Projectname''​ project files in the main, trunk directory (I think that's the way it should be set up). Of course, this will only work once the project account manager have your public key and has set it up. to list the ''​Projectname''​ project files in the main, trunk directory (I think that's the way it should be set up). Of course, this will only work once the project account manager have your public key and has set it up.
- 
Navigation

The best way to find something here is to use the search box in the upper right or the site index link below.

Print/export
Mobile QR Link