Creating Source Version Control Repositories
This document briefly describes how you can use the tools at https://my.cae.wisc.edu/ to create a repository.
New version control repositories can be created using the CAE My Account Tools found here: https://my.cae.wisc.edu/tools/account/repos/. Further details on the settings can be found below.
If you have data from an existing filesystem based repository that you would like imported please contact firstname.lastname@example.org for assistance.
It should be noted that, like other CAE-offered tools such as vhosts, dbs, etc., repository creation is by default limited to faculty and staff. However, once a repository is created the owner can give ownership of the repo to anyone, including students. Using repositories is by default available to almost all CAE accounts. See below for more details.
To control access each repository has associated with it the following:
A user with full access to the repository instance. Ownership can be given away to another user if desired.
- Editing Group
A group of CAE accounts that have access to write to the repository instance. Editing group members should also be added to the read group in order to read the repository instance.
- Editing Networks
A set of networks (eg: CoE, UW, Any) that write operations are restricted to. The default is UW campus networks.
- Read Group
A group of CAE accounts that have access to read the repository instance.
- Read Networks
A set of networks (eg: CoE, UW, Any) that read operations are restricted to. The default is UW campus networks.
There are also a handful of other settings that can tweak the behavior and interpretation of these settings.
- Read Satisfy
Governs whether both Read Group and Read Networks are required to gain read access, or if either is sufficient.
- All (the default)
This allows read access only to members of the Read Group who are also authenticating from a host on the Read Networks.
This allows read access to any CAE account on the Read Networks. Whatever has been set for Read Group membership is effectively ignored.
This allows anonymous read access from any of the Read Networks OR read access to any member of the Read Group. This setting can be used to make fully publicly available repositories if, for example, the Read networks are set to Any as well.
- All (the default)
Some other options are also available after repository creation for controlling
push hook behavior. See
Source Version Control Repositories Customization and Hooks
for more details.