Svn notes - Revision history

Leo: /* Integration with TRAC */

2011-08-18T20:55:44Z

‎Integration with TRAC

Leo: /* Server preliminaries */

2011-05-26T12:35:16Z

‎Server preliminaries

Leo: /* Creating a basic SVN repository */

2011-05-26T12:34:31Z

‎Creating a basic SVN repository

Leo: /* Single unix account, multiple users access with public key authorization */

2010-10-27T14:34:11Z

‎Single unix account, multiple users access with public key authorization

Leo: /* Access */

2010-10-27T14:33:42Z

‎Access

Leo: /* Single unix account, multiple users access with public key authorization */

2010-10-27T14:31:47Z

‎Single unix account, multiple users access with public key authorization

Leo at 14:11, 27 October 2010

2010-10-27T14:11:38Z

Leo: /* SVN client (GUIs) */

2010-10-01T14:23:12Z

‎SVN client (GUIs)

Leo: /* SVN client (GUIs) */

2010-10-01T14:22:55Z

‎SVN client (GUIs)

Leo at 09:52, 27 July 2010

2010-07-27T09:52:42Z

@@ Line 105: / Line 105: @@
  MSG=$(svnlook log -r $REV /var/svn/myproj)
  /usr/bin/python /usr/local/bin/trac-post-commit-hook -p "$TRAC_ENV" -r "$REV" -m $MSG
+== Remove all .svn directories ==
+Like this:
+ rm -rf `find . -type d -name .svn`

@@ Line 16: / Line 16: @@
 == Server preliminaries ==
-It might be a good idea to create a "subversion" group and add www-data as a user to it.
+It might be a good idea to create a "subversion" group and add yourself (the svn client user) and www-data as a user to it.
  sudo addgroup subversion

@@ Line 13: / Line 13: @@
 * For windows use [http://tortoisesvn.net '''TortoiseSVN''']. There is a nice [http://tortoisesvn.net/ssh_howto FAQ for TortioseSVN with ssh].
+== Server preliminaries ==
+It might be a good idea to create a "subversion" group and add www-data as a user to it.
+ sudo addgroup subversion
+ sudo usermod -a -G subversion www-data
 == Creating a basic SVN repository ==
@@ Line 27: / Line 34: @@
  sudo chown -R www-data:subversion myproject
  sudo chmod -R g+rws myproject
 == Global ignore ==

@@ Line 43: / Line 43: @@
  SVN_SSH='ssh -l username' rapidsvn
-== Single unix account, multiple users access with public key authorization ==
+== Single unix account, multiple user access with public key authorization ==
 ====Setup====

@@ Line 81: / Line 81: @@
  mysvn svn ci         ...check in the new file and any modifications
  mysvn svn up         ...update your working copy from the svn, in case someone else has done some changes.
- mysvn rapidsvn       ...fire up IDE for svn project
+ mysvn rapidsvn       ...fire up an IDE for the svn project
 ====Access from Windows====

@@ Line 45: / Line 45: @@
 == Single unix account, multiple users access with public key authorization ==
+====Setup====
 Here is a description on how to set up svn on a single unix account and using private-public key authorization for multiple users.
 * http://svn.collab.net/repos/svn/trunk/notes/ssh-tricks
@@ Line 60: / Line 61: @@
 If you do not know how to generate the keys, here is how: [[Ssh_with_a_private-public_key]]
+====Access====
+Suppose you have created the svn account under the user svnuser, and the repository is stored on the server example.com at /home/svnuser/svn/the-project.
+Suppose John wants to access the svn and has given his public key so that it is defined in the  .ssh/authorized_keys file as follows:
+  command="/usr/bin/svnserve -t -r /svn/the-project --tunnel-user=John",no-port-forwarding,no-agent-forwarding,no-X11-forwarding,no-pty ssh-rsa AAAABlotsmoregookhere= address@example.com
+Then John can check out the repository from virtually any Linux account as follows:
+ SVN_SSH="ssh -l svnuser" svn co svn+ssh://example.com
+This is rather long typing, so I suggest you set up an alias in your .bashrc or wherever:
+ alias mysvn='SVN_SSH="ssh -l svnuser" '
+and use it like this:
+ mysvn svn co svn+ssh://example.com myproj      ...checks out the repository the first time
+ cd myproj
+ gedit myfile1        ...create and edit a new file
+ svn add myfile1      ...mark it to be added to the repository
+ mysvn svn ci         ...check in the new file and any modifications
+ mysvn svn up         ...update your working copy from the svn, in case someone else has done some changes.
+ mysvn rapidsvn       ...fire up IDE for svn project
+====Access from Windows====
+You can access the repository from windows as well. For example, using putty key agent and tortoiseSVN.
+Note that you need to specify the svn repository path with the proper username, e.g. svnuser as in the example above.
 == Integration with TRAC ==

@@ Line 1: / Line 1: @@
+{{TocRight}}
-Good start for basic subversion info is at https://help.ubuntu.com/community/Subversion
+A good start for basic subversion info is at https://help.ubuntu.com/community/Subversion
 You may also want to read [http://www.cyberciti.biz/faq/howto-linux-add-user-to-group how to add a group or user to a group].

@@ Line 11: / Line 11: @@
 * [http://wiki.rabbitvcs.org/wiki/install/ubuntu '''RabbitVCS'''] - inspired by TortoiseSvn, but for Linux. However, if you have large or several repositories checked out in a directory that you are trying to open in nautilus, the latter may hang for a long time while the Rabbit goes through all the subdirectories.
-* For windows use [http://tortoisesvn.net TortoiseSVN]. There is a nice [http://tortoisesvn.net/ssh_howto FAQ for TortioseSVN with ssh].
+* For windows use [http://tortoisesvn.net '''TortoiseSVN''']. There is a nice [http://tortoisesvn.net/ssh_howto FAQ for TortioseSVN with ssh].
 == Creating a basic SVN repository ==

@@ Line 57: / Line 57: @@
 If you do not know how to generate the keys, here is how: [[Ssh_with_a_private-public_key]]
+== Integration with TRAC ==
+You can make TRAC close messages when committing in svn by mentioning the ticket number like "This fixes #17".
+You will need to find (and install) the appropriate trac-post-commit-hook script for your TRAC version.
+Here is an example of the
+/var/svn/myproj/hooks/post-commit file:
+ #!/bin/sh
+ REPOS="$1"
+ REV="$2"
+ TRAC_ENV="/var/trac/mytrac"
+ MSG=$(svnlook log -r $REV /var/svn/myproj)
+ /usr/bin/python /usr/local/bin/trac-post-commit-hook -p "$TRAC_ENV" -r "$REV" -m $MSG