Subversion Web Interface
Subversion ViewVC Web Interface
Authentication & Authorization
Authentication, who can connect to the server, is handled by Rice. Anyone with a netId can authenticate to the Subversion server or web interface, this includes guest accounts. Authentication can be forced by using the https protocol when accessing the server.
Authorization, who can access the repository, is controlled by the repository owner and their delegates. Each repository is created with a /rice_config directory. This directory contains a file named access_file. The access_file controls who has access to that specific repository. Changes to the access_file take up to 5 minutes to become active on the server. Please see the file access_file.readme which is also located in the /rice_config directory for a simple explanation of the format of this file. For more information, please read the Subversion Book linked to on the right.
This resource is available 24 hours a day most days. If we need to take the system down for an extended time an email will be sent to the repository owners regarding the date and time of the outage. The system will occasionally need to be taken down for routine maintenance and repair. Please see the Subversion page for information about regularly scheduled maintenance times.
Each repository is backed up with a hot copy backup nightly, replacing the previous backup. Upon repository deletion, the last backup for that repository is kept for a maximum of six months.
Each repository is owned by a primary owner. If this primary owner becomes inactive, any repositories owned by this owner will begin down the cleanup process. If control of the repository is shared with others, i.e. other people have write access to the /rice_config folder within the repository, then they will be offered the opportunity to become the new owner of the repository which will remove it from deletion processing.
Please see Repository Cleanup for more information on the cleanup process.