This document briefly describes how to access a repository.
Repositories can be accessed by clients via
https:// urls as shown below. Some of them can
also be viewed using a browser and the native repository display tools.
To illustrate the service we provide a couple of example repositories.
They are currently restricted to UW networks and CAE accounts.
# svn checkout https://subversion.cae.wisc.edu/svn/EXAMPLE_SVN_PROJECT
# svn checkout https://subversion.cae.wisc.edu/svn/EXAMPLE_SVN_PROJECT # cd EXAMPLE_SVN_PROJECT # echo "example text" >> example.txt # svn add example.txt # svn commit -m "adding example file to the repository" example.txt
# git clone https://git.cae.wisc.edu/git/EXAMPLE_GIT_PROJECT
user.emailsetting to something like
pushoperations can be authenticated and emails forwarded properly.
# git config user.email firstname.lastname@example.org
# git clone https://git.cae.wisc.edu/git/EXAMPLE_GIT_PROJECT # cd EXAMPLE_GIT_PROJECT # echo "example text" >> example.txt # git add example.txt # git commit -m "adding example file to the repository" example.txt # git push origin master
NOTE: CAE does not support files larger than 100MB in repositories. You may experience problems, such as errors like the following reported:
fatal: The remote end hung up unexpectedly fatal: protocol error: bad pack header error: RPC failed; result=18, HTTP code = 200If you do, you can try adding the following to your
[core] packedGitLimit = 2G packedGitWindowSize = 1G bigFileThreshold = 50M [pack] threads = 1 windowMemory = 2G
Please note that all access to these repositories is accomplished via
https:// URLs - no direct
filesystem access is provided, though we can assist in importing legacy repositories if necessary. For
more details on accessing the individual repositories via
https:// please see the individual
repository's documentation links listed above.
By default, all authentication uses your CAE account credentials (we can make accounts for outside
parties if need be). However, some clients, such as
svn, default to storing your
repository passwords in clear text. Since this isn't secure, we also provide the option for each
account to have a different password for each repository.