6.1. Access to Rocks Source Code

The source code for Rocks is available from a public read-only GIT repository. As of Rocks 5.7 GIT (git) is installed on your frontend machine, for older version of Rocks (or non-Rocks platforms) you will need to install the Git package yourself. You can download rpm packages from the EPEL Red Hat web site at http://dl.fedoraproject.org/pub/epel/5/x86_64/repoview/git.html

Git is a a distributed source control system. Several tutorials are provided on the GIT web site http://git-scm.com/documentation. Fundamentally, distributed source control turns your checked out source code from a read-only copy into a repository and then grants read-write access to others based on your checked out repository. In the context of Rocks this means individual Roll developers can independently control who has access to their code.

You can use the Github Web interface to view the source code using your browser at https://github.com/rocksclusters/. Each Roll has its own repository named after the Roll. So if you need to checkout the Base roll you should checkout the repository called base under the Rocks Github web page (in this example https://github.com/rocksclusters/base) To check out the current source code you will first need to clone one of the read-only repository listed on the main web page of the Github web site. This operation can take several minutes to complete.

 $ git clone http://github.com/rocksclusters/base;
Cloning into 'base'...
 $ cd base
 $ git status
# On branch master
nothing to commit (working directory clean)
 $ git status
# On branch master
# Changes not staged for commit:
#   (use "git add <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#	modified:   DESCRIPTION
no changes added to commit (use "git add" and/or "git commit -a")