Git server

From LWP-Wiki
Jump to: navigation, search

This describes how to create repositories on the git server of the RUG and enable other people to access them over the internet.

Familiarity is assumed with Git and SSH.

Repository directory

Staff members can get a directory in which they can create repositories.

To get an account with a repository directory, please provide us with:

Your e-mail address
For accounts that can create repositories, addresses are required.
Your SSH public key
This is a small text file (~ 1kb). If you use OpenSSH, it is by default ~/.ssh/ Getting an SSH public key is outside the scope of this manual.
Directory name
This will become part of the URL to your repositories. An obvious name could be the acronym of your department, project, or just your initials.

Checking access

Run this command to check your access to the server:

ssh info

Anybody whose SSH public key was registered with the server can run this command. If successful, it lists the repositories you have access to, and your permissions to them.

Example output:

C    abc/..*
R W  one/example
R    doc

Which means:

  • You can create repositories inside the directory abc.
  • You can read and write to a repository called one/example.
  • You can read the repository doc.

Creating a repository

To create a new repository, just clone from the directory where you have permissions to create repositories. Repositories that do not exist yet, will be created on the fly:

git clone

Breakdown of the URL:

The username for SSH. This is always “git”.
DNS name of the Version Control Server. This is always “”.
This is the directory where you can create repositories.
Name of the (new) repository.

When you create a repository, you will be registered as the owner of it. This enables you to grant access permissions to other persons.

Granting access to others

To enable third party persons to access the server, please provide their:

  • E-mail address
  • SSH public key

At this moment new accounts will need to be registered on the server manually by the server admins. In the future a web application may automate this.

Once they’re registered, you can grant them access to repositories you own (or are allowed to administrate) by assigning roles to their e-mail address.

E.g. to enable John Doe to write to your repository abc/example, run the perms command using SSH like this:

ssh perms abc/example + WRITERS

In this command, “WRITERS” is called a role. If you would want to grant John Doe only read access to the repository, you could specify “READERS” instead.

To revoke a role instead, replace the ‘+’ in the command with a ‘-’:

ssh perms abc/example - WRITERS


There are more levels of access than just “READERS” and “WRITERS”. Here is the entire list of roles with their permissions:

Only reading is allowed, i.e.:
  • clone
  • fetch
  • pull
In addition to what READERS can do:
  • Fast-forward push (except to the “master” branch).
  • Create new branches.
  • Create tags.
In addition to what WRITERS can do:
  • Fast-forward push to “master”.
In addition to what MASTERS can do:
  • Delete branches.
  • Delete tags.
  • Non fast-forward push, i.e. push amended commits, rebased or rewound branches.
In addition to what MANAGERS can do:
  • Managing access to the repository by assigning/revoking roles, just like the owner of the repository.

If more than one role is assigned, the role which allows the most will be in effect.

To list which roles are assigned for a repository, run the perms with the -l option command using SSH:

ssh perms abc/example -l
Note #1:
The -l option should be the last argument on the command line.
Note #2:
Do not omit the -l option without knowing what you’re doing! This will invoke “batch mode” and if you leave the input empty (even by pressing ctrl-c) it will erase all permissions! The only correct way to bail out of this is to enter literally: cancel and press enter.

Further information