"It's basically GitHub"
It is recommended to setup SSH keys so that you do not have to enter your password each time you push to a repo. Once you have uploaded your public key, add the following to your ~/.ssh/config:
Host csclub.uwaterloo.ca HostName csclub.uwaterloo.ca IdentityFile ~/.ssh/id_rsa User git
(Replace ~/.ssh/id_rsa by the location of your private SSH key.) Now you should be able to clone, push and pull over SSH.
We are running a CI server at https://ci.csclub.uwaterloo.ca. It uses OAuth via Gitea for logins, so you need to have logged in to Gitea first. See https://docs.drone.io/ for documentation. All you have to do is create a .drone.yml file in your repo, then enable CI on the repo from the CSC Drone website. There is an example here.
Pushing and pulling from the filesystem
(for syscom only)
If you need to keep the ability to push/pull from the filesystem, in addition to Gitea, you will need to take the following steps. In this example, we are migrating a repo called 'public/repo.git', which is a folder under /srv/git on caffeine (which is a symlink to /users/git). The way we're doing this right now is kind of hacky, but it works:
- Clone the original repo locally:
git clone /srv/git/public/repo.git
- Delete the old repo (from phosphoric-acid, which has no_root_squash):
rm -rf /srv/git/public/repo.git
- Create a new repo with the name 'repo' from the Gitea web UI. This should create a bare repository at
/srv/git/public/repo.git. (Make sure you choose the 'public' org from the dropdown.)
Push the original repo to the new remote:
cd repo git remote add gitea https://git.csclub.uwaterloo.ca/public/repo.git git push gitea master
Change file permissions:
chown -R git:git /srv/git/public/repo.git chmod -R g+w /srv/git/public/repo.git
You will need to do this from phosphoric-acid (due to NFS root squashing).
Note that the repo folder SHOULD be owned by git:git. Anything else will likely break Gitea. (If a user pushes something to the folder and their umask doesn't allow group members to read, for example, then Gitea will be unable to read the repo.)
This means that only trusted users should be in the git group - ideally, only syscom members.