Subversion - Revision history

Gr0x0rd: /* Configuring Software - Subversion */

2011-05-10T16:17:29Z

Configuring Software - Subversion

Gr0x0rd: /* Configuring Software - Subversion */

2011-05-10T16:15:41Z

Configuring Software - Subversion

Gr0x0rd: /* Configuring Software - Subversion */

2011-05-09T17:15:29Z

Configuring Software - Subversion

Gr0x0rd: /* Configuring Software - Subversion */

2011-05-09T17:04:43Z

Configuring Software - Subversion

Gr0x0rd: /* Configuring Software - Subversion */

2011-03-13T22:51:29Z

Configuring Software - Subversion

Gr0x0rd: /* Configuring Software - Subversion */

2011-03-13T22:51:16Z

Configuring Software - Subversion

Gr0x0rd: /* Configuring Software - Subversion */

2011-03-13T22:34:36Z

Configuring Software - Subversion

Gr0x0rd: Created page with "== Configuring Software - Subversion == If you do any type of development work, you'll probably want to use some type of version control, especially if you have multiple people …"

2011-03-13T22:26:07Z

Created page with "== Configuring Software - Subversion == If you do any type of development work, you'll probably want to use some type of version control, especially if you have multiple people …"

New page

== Configuring Software - Subversion ==

If you do any type of development work, you'll probably want to use some type of version control, especially if you have multiple people working on the project or if you just want to take advantage of the easy way to deploy code.
'''$''' sudo emerge -av subversion
Check that that apache2 USE flag is enabled before performing the emerge. After the emerge has completed, you can create a group for users who will have access to the repositories, including yourself. However, making yourself or any other users members of the apache group should be sufficient if you are wanting to use apache to leverage svn.
'''$''' sudo gpasswd -a <username> apache
Create a repository. Substitute your repository's name in the place of ''reponame''.
'''$''' sudo svnadmin create --fs-type fsfs /var/svn/''reponame''/
Set permissions on the repository and subfolders.
'''$''' sudo chown -R root:apache /var/svn/''reponame''/
'''$''' sudo chmod -R g-w /var/svn/''reponame''/
'''$''' sudo chmod -R g+rw /var/svn/''reponame''/db
'''$''' sudo chmod -R g+rw /var/svn/''reponame''/locks

← Older revision		Revision as of 16:17, 10 May 2011
Line 1:		Line 1:
−	== ~~Configuring Software -~~ Subversion ==	+	== Installing Subversion ==

	If you do any type of development work, you'll probably want to use some type of version control, especially if you have multiple people working on the project or if you just want to take advantage of the easy way to deploy code.		If you do any type of development work, you'll probably want to use some type of version control, especially if you have multiple people working on the project or if you just want to take advantage of the easy way to deploy code.

@@ Line 8: / Line 8: @@
   '''$''' sudo gpasswd -a <username> apache
 Create a home for subversion. In this example we'll use ''/var/svn/''.
-  '''$''' sudo mkdir /var/svn
+  '''$''' sudo mkdir /var/svn ; sudo mkdir /var/svn/conf
 Create a repository. Substitute your repository's name in the place of ''reponame''.
   '''$''' sudo svnadmin create --fs-type fsfs /var/svn/''reponame''/
@@ Line 53: / Line 53: @@
 Restart apache to apply the settings.
   '''$''' sudo /etc/init.d/apache2 restart
 == Using subversion ==
 You should now be able to view the repository you created at http://''yourservername''/svn/ after supplying your username and password. Next, navigate to the folder where your code is, and import the initial revision into the repository. Assuming the project code is owned by the ''apache'' user

@@ Line 53: / Line 53: @@
 Restart apache to apply the settings.
   '''$''' sudo /etc/init.d/apache2 restart
 You should now be able to view the repository you created at http://''yourservername''/svn/ after supplying your username and password. Next, navigate to the folder where your code is, and import the initial revision into the repository. Assuming the project code is owned by the ''apache'' user
   '''$''' sudo -u apache svn import . http://''yourservername''/svn/''reponame''/ -m 'Initial import'
@@ Line 68: / Line 69: @@
   '''$''' sudo -u apache svn update
 A very handy cheat sheet for subversion commands is available [[http://www.abbeyworkshop.com/howto/misc/svn01/ here]].

@@ Line 65: / Line 65: @@
 To check out the latest revision
   '''$''' sudo -u apache svn update
-A very handy cheat sheet for subversion commands is available [[http://www.abbeyworkshop.com/howto/misc/svn01/ | here]].
+A very handy cheat sheet for subversion commands is available [[http://www.abbeyworkshop.com/howto/misc/svn01/ here]].

@@ Line 40: / Line 40: @@
 </Location>
 </pre>
+Add the svnusers group to the apache group.
-Next, navigate to the folder where your code is, and import the initial revision into the repository.
+ '''$''' sudo usermod -G svnusers -a apache
-  '''$''' sudo svn import . file:///var/svn/''reponame''/ -m 'Initial import'
+To put some basic security on the repository we'll use htpasswd2. Replace ''username'' with your intial user.

@@ Line 4: / Line 4: @@
   '''$''' sudo emerge -av subversion
 Check that that apache2 USE flag is enabled before performing the emerge. After the emerge has completed, you can create a group for users who will have access to the repositories, including yourself. However, making yourself or any other users members of the apache group should be sufficient if you are wanting to use apache to leverage svn.
   '''$''' sudo gpasswd -a <username> apache
 Create a repository. Substitute your repository's name in the place of ''reponame''.
@@ Line 12: / Line 14: @@
   '''$''' sudo chmod -R g+rw /var/svn/''reponame''/db
   '''$''' sudo chmod -R g+rw /var/svn/''reponame''/locks