RSE SVN: Difference between revisions
| Line 32: | Line 32: | ||
ssh-keygen -t rsa | ssh-keygen -t rsa | ||
ssh-copy-id -i .ssh/id_rsa.pub | ssh-copy-id -i .ssh/id_rsa.pub [timmy_username]@timmy.elektro.dtu.dk | ||
then (after a final password) you should be able to do a | then (after a final password) you should be able to do a | ||
Revision as of 17:30, 22 May 2010
RSE projects are all developmental projects, with ongoing improvement and research.
For proper version management, backup and sharing, the projects are managed in a central SVN repository, hosted by the DTU Elektro production server Timmy.
SVN Access
To get access to the RSE SVN, you must have an account on the timmy server and be a RSE group member.
The SVN is accessed using the svn+ssh protocol, with the following connection string:
svn+ssh://[timmy username]@timmy.elektro.dtu.dk/home/project-users/rse/svnrepo
As the SVN is run through SSH, you will be requested to input your SSH password MANY times, until you have setup your computer with a shared SSH key.
Handling SVN projects
Managing the projects in SVN should be done according to the guidelines in the SVN book[1]. It is really good and usefull reading.
At a prevoius robot-meeting, there was given an introduction for SVN useage.
The slides from the presentation can be found here: Media:SVN_Best_practice.pdf
A great toturial for generating shared SSH keys can be found in the article No More Passwords (with SSH) eller password-less login
The method is in short (and follow instructions):
ssh-keygen -t rsa ssh-copy-id -i .ssh/id_rsa.pub [timmy_username]@timmy.elektro.dtu.dk
then (after a final password) you should be able to do a
svn update
and all the rest (including ssh-login to timmy) without being bugged with passwords.
