Cheiron

1. General
   1. News
   2. Blogs
   3. Mission
   4. Guidelines
2. Projects
   1. JSC
   2. Seven
   3. Utils
3. Participate
   1. Overview
   2. Repositories
   3. Mailing lists
   4. References
   5. Issue tracking
4. Misc
   1. License
   2. Credits
   3. Legal

Source code repositories

We provide an SSH tunnel to our Perforce source code repositories for developers with the committer status, for others we provide a web based read-only view on the repository. Upon receiving the committer status you have to sent your public SSH key and can connect by following the instructions below.

It is possible for non committers to get read-only access on the Perforce reposity, through the mechanism described below, by sending a request to the developer mailing list of the project that explains why the source code downloads are not sufficient.

Download the source

Most users of the source code probably don't need to have day to day access to the source code as it changes. For these users we provide easy to unpack source code downloads via the individual project homepages, in most cases on a daily basis when changes to the source code have been made.

Connecting to Perforce repository with SSH

Committers can access the Perforce repository by using SSH with local port forwarding. Authentication of committers is key based, therefore you have to create a private/public key pair and send your public SSH key to the Cheiron project.

Once your public key has been setup for the generic user 'scm-ssh' on the server 'cheiron-scm.merangar.com' you can connect to the Cheiron Perforce repository by means of local port forwarding with SSH to 'perforce.merangar.com' at port 1666:

The above command allows you to connect to port 1666 on your local machine as if it were the Perforce server, all trafic however is transparently forwarded to the Perforce Server at 'perforce.merangar.com' at port 1666. The '-n' flag says to not read from stdin, '&' puts the process in the background and the 'sleep' option prevents the session from timing out. In the above we used port 1666 as the local port, but of course you are free to use any port you wish.

If you are using Windows and PuTTy as your SSH client you can follow these instructions to setup local port forwarding.

Note: you can't obtain an interactive shell for the user 'scm-ssh' with using public key authentication.