Code repositories
The VirtualRDC offers to VirtualRDC and RDC researchers, Subversion code repositories.
What is Subversion?
In a nutshell, Subversion allows to
- keep a log of all changes made to your code
- roll back changes to any one of registered checkpoints
- share the code between multiple users
- distinguish users that can modify code, and those that can only read the code
- branch off versions that henceforth share a common ancestor but follow somewhat separate development.
A comparison of different VCS can be found here.
How can I use it
- First, you need to know where to access one. See below
- You need client software:
- Most Unix/Linux installations have command-line clients available.
- TortoiseSVN (http://tortoisesvn.tigris.org/) is a Windows client that works just great. Very transparent and easy to use. Needs administrator rights to be installed.
- eSVN (http://esvn.umputun.com/) is a cross-platform GUI
- SmartSVN (http://smartcvs.com/smartsvn/download.html) is a Java client. It works without installation on Windows if you use the Java Webstart link (here), you need Java and Java Webstart installed). You do not need to be Administrator to use the installer to install it permanently. Verified to work on Linux. (Note that this is free, but not open-source software)
Available repositories
- Public VRDC code repository
- Browseable interface: http://repository.vrdc.cornell.edu/viewcvs-public/
- Full access interface (no writes): http://repository.vrdc.cornell.edu/public/
- Test code repository. This is freely accessible for testing and learning purposes, but gets wiped and rebuilt every night. When prompted for a login, use ‘testuser’/'testuser’.
- Restricted-access code repositories with restricted access:
- VirtualRDC code repository (full access interface:
http://repository.vrdc.cornell.edu/VRDC/{CODE} )
- VirtualRDC code repository (full access interface:
Access policy
We maintain collaborative code projects here. Some are publicly available, some are only accessible using Subversion clients, and finally some require passwords for both checkout and commits. Those interested can find out more details on the VirtualRDCWiki
or by contacting VirtualRDC administrators.