Hosting Subversion Repositories - Revision history

Steve410.cs.jhu.edu: /* First, Tell IT Support */

2016-03-03T17:34:49Z

First, Tell IT Support

2014-09-15T13:14:04Z

Give Yourself Access to the Repository

2014-09-12T15:25:10Z

2014-09-12T15:24:22Z

First, Tell IT Support

2014-09-12T15:23:26Z

First, Tell IT Support: Clarify that people can do all of their setup while waiting for us to do ours.

2014-09-12T15:08:41Z

Categorize.

2014-09-12T14:13:24Z

Add the Person to the .svnaccess File

2014-09-12T14:10:05Z

Copy an Existing Repository, if Needed

2014-09-12T14:09:51Z

Copy an Existing Repository, if Needed

2014-09-12T14:09:24Z

Copy an Existing Repository, if Needed

@@ Line 19: / Line 19: @@
 There are a few things you have to do just once, when you want to get all of this started.
-=== First, Tell IT Support ===
+=== First, Tell CS IT Support ===
 There are some changes that need to be made to the department's webserver in order for this to work, so the first thing to do is for you to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] and let us know that you need to set up a hosted Subversion repository, so that we can do our part.

@@ Line 149: / Line 149: @@
 </pre>
-The tilde ("~") needs to be in that first line; only replace "''your-account''".
+The tilde ("~") needs to be in that first line; only replace "''your-account''" and "''your-repository''".
 == Things You Need to do For Each Collaborator ==

← Older revision		Revision as of 15:25, 12 September 2014
Line 1:		Line 1:
−	This page describes how to set up, on the CS Department servers, Subversion repositories that you can use to collaborate with other people (whether or not those other people are at Johns Hopkins). This is a somewhat complicated process. If you're comfortable with any of the distributed version control systems (Git, Mercurial, Bazaar, Darcs), you should use those instead, as the setup is a lot simpler. Instructions for those systems can be found on our general [[Version Control on the CS Systems\|version control page]].	+	This page describes how to set up, on the CS Department servers, Subversion repositories that you can use ''to collaborate with other people'' (whether or not those other people are at Johns Hopkins). This is a somewhat complicated process. If you're comfortable with any of the distributed version control systems (Git, Mercurial, Bazaar, Darcs), you should use those instead, as the setup is a lot simpler. Instructions for those systems can be found on our general [[Version Control on the CS Systems\|version control page]].

	== Overview ==		== Overview ==

@@ Line 21: / Line 21: @@
 === First, Tell IT Support ===
-There are some changes that need to be made to the department's webserver in order for this to work, so the first thing to do is for you to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] and let us know that you need to set up a hosted Subversion repository.
+There are some changes that need to be made to the department's webserver in order for this to work, so the first thing to do is for you to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] and let us know that you need to set up a hosted Subversion repository, so that we can do our part.
 You can continue with the rest of the instructions on this page while you wait for a response, but you won't be able to use your repositories via <tt><nowiki>https://</nowiki>www.cs.jhu.edu</tt> URLs until we've made the necessary changes on our end.  We'll email you once we've completed those changes.

← Older revision		Revision as of 15:23, 12 September 2014
Line 22:		Line 22:

	There are some changes that need to be made to the department's webserver in order for this to work, so the first thing to do is for you to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] and let us know that you need to set up a hosted Subversion repository.		There are some changes that need to be made to the department's webserver in order for this to work, so the first thing to do is for you to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] and let us know that you need to set up a hosted Subversion repository.
		+
		+	You can continue with the rest of the instructions on this page while you wait for a response, but you won't be able to use your repositories via <tt><nowiki>https://</nowiki>www.cs.jhu.edu</tt> URLs until we've made the necessary changes on our end. We'll email you once we've completed those changes.

	=== Create a Directory for the Repositories ===		=== Create a Directory for the Repositories ===

← Older revision		Revision as of 15:08, 12 September 2014
Line 182:		Line 182:

	If you have any problems with the instructions or just need extra help, please feel free to email [mailto:support@cs.jhu.edu support@cs.jhu.edu].		If you have any problems with the instructions or just need extra help, please feel free to email [mailto:support@cs.jhu.edu support@cs.jhu.edu].
		+
		+	[[Category:Software]]

@@ Line 167: / Line 167: @@
 === Add the Person to the .svnaccess File ===
-The short version of this step is to edit your <tt>~/public_html/svn/.svnaccess</tt> file, find the section for the repository the person should be able to access, and add a line for them in that section that looks like this:
+The short version of this step is to edit your <tt>~/public_html/svn/.svnaccess</tt> file, find the section for the repository the person should be able to access, and add a line for them in that section that looks like this (replacing ''their-account'' with the person's account name):
   ''their-account'' = rw

@@ Line 128: / Line 128: @@
 If you have an existing repository (located elsewhere) that you want to move to the CS webserver, you need to copy its data over.  (If you're starting from scratch, you can skip this step.)
-You do need to create an empty repository in <tt>~/.svnrepos</tt> first.  Once that's done, you can use ''<tt>svnadmin dump</tt>'' on the old system and ''<tt>svnadmin load</tt>'' on a CS Linux client to move the data over.
+You '''do''' need to create an empty repository in <tt>~/.svnrepos</tt> first.  Once that's done, you can use ''<tt>svnadmin dump</tt>'' on the old system and ''<tt>svnadmin load</tt>'' on a CS Linux client to move the data over.
 If the old system is also Unix-based, you can often elegantly transfer the data by running the following command ''on the old system'':