Hosting documentation/Source Code Management

From Bioinformatics.Org Wiki

< Hosting documentation(Difference between revisions)
Jump to: navigation, search
(Added "see also")
m (SSH Developer Access)
 
(2 intermediate revisions not shown)
Line 1: Line 1:
-
Your project may create Subversion and CVS repositories, not just a directory on a master repository. This means that your SVN and CVS logs, history files, and behavior can be unique to your repository.
+
Your group may create Source Code Management (SCM) repositories, not just a directory on a master repository. This means that your logs, history files, and behavior can be unique to your repository.
-
Anonymous Subversion and CVS Access
+
==Anonymous access==
-
We open up the repositories for anonymous access through the standard protocol implementations. No passwords are sent in anonymous SVN and CVS access.
+
We open up the repositories for anonymous access through the standard protocol implementations. No passwords are sent in anonymous access.
-
SSH Developer Access
+
==SSH Developer Access==
-
The most common method of accessing Subversion and CVS repositories remotely is through the respective protocol implementations. These methods are insecure, however, as they broadcasts passwords in plain text over the Internet.
+
The most common method of accessing SCM repositories remotely is through the respective protocol implementations. These methods are insecure, however, as they broadcasts passwords in plain text over the Internet.
-
We have chosen to allow developers to access the SVN and CVS reponsitories through SSH, which the respective clients can easily do once SSH is installed.
+
We have chosen to allow developers to access the repositories through SSH, which the respective clients can easily do once SSH is installed.
-
Please see the [[Subversion]] and [[CVS]] documentation for more information.
+
Please see the documentation for the specific SCM tools for more information:
 +
 
 +
* [[CVS]]
 +
* [[Subversion]]
 +
* [[Git]]
==See also==
==See also==
* [[Hosting documentation]]
* [[Hosting documentation]]

Latest revision as of 16:27, 2 May 2013

Your group may create Source Code Management (SCM) repositories, not just a directory on a master repository. This means that your logs, history files, and behavior can be unique to your repository.

Anonymous access

We open up the repositories for anonymous access through the standard protocol implementations. No passwords are sent in anonymous access.

SSH Developer Access

The most common method of accessing SCM repositories remotely is through the respective protocol implementations. These methods are insecure, however, as they broadcasts passwords in plain text over the Internet.

We have chosen to allow developers to access the repositories through SSH, which the respective clients can easily do once SSH is installed.

Please see the documentation for the specific SCM tools for more information:

See also

Personal tools
Namespaces
Variants
Actions
wiki navigation
Toolbox