Git server - Revision history

Sebastian: Mention GitLab server git.lwp.rug.nl

2024-06-17T13:22:25Z

Mention GitLab server git.lwp.rug.nl

← Older revision		Revision as of 13:22, 17 June 2024
Line 2:		Line 2:
	__TOC__		__TOC__

	This describes how to create repositories on the ~~git~~ server of the RUG and enable other people to access them over the internet.		This describes how to create repositories on the [https://vcs.service.rug.nl Git server of the RUG (vcs.service.rug.nl)] and enable other people to access them over the internet.

			The LWP team additionally provides a [https://git.lwp.rug.nl GitLab instance, git.lwp.rug.nl], running within the CIT facilities. The university-wide login with S/P-number can be used to use this server.

			= vcs.service.rug.nl =

	Familiarity is assumed with Git and SSH.		Familiarity is assumed with Git and SSH.

	= Repository directory =		== Repository directory ==

	Staff members can get a directory in which they can create repositories.		Staff members can get a directory in which they can create repositories.
Line 19:		Line 23:
	: 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.		: 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 =		== Checking access ==

	Run this command to check your access to the server:		Run this command to check your access to the server:
Line 37:		Line 41:
	* You can read the repository <code>doc</code>.		* You can read the repository <code>doc</code>.

	= Creating a repository =		== 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:		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:
Line 55:		Line 59:
	When you create a repository, you will be registered as the owner of it. This enables you to grant access permissions to other persons.		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 =		== Granting access to others ==

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

	<pre>ssh git@vcs.service.rug.nl perms abc/example - WRITERS john.doe@somehere.net</pre>		<pre>ssh git@vcs.service.rug.nl perms abc/example - WRITERS john.doe@somehere.net</pre>
	== Roles ==
			=== Roles ===

	There are more levels of access than just “READERS” and “WRITERS”. Here is the entire list of roles with their permissions:		There are more levels of access than just “READERS” and “WRITERS”. Here is the entire list of roles with their permissions:
Line 110:		Line 115:
	: Do not omit the <code>-l</code> option without knowing what you’re doing! This will invoke “batch mode” and if you leave the input empty (even by pressing <code>ctrl-c</code>) it will erase all permissions! The only correct way to bail out of this is to enter literally: <code>cancel</code> and press <code>enter</code>.		: Do not omit the <code>-l</code> option without knowing what you’re doing! This will invoke “batch mode” and if you leave the input empty (even by pressing <code>ctrl-c</code>) it will erase all permissions! The only correct way to bail out of this is to enter literally: <code>cancel</code> and press <code>enter</code>.

	= Further information =		== Further information ==

	* “Gitolite” is used for hosting ~~git~~ on this server. So for all the details, refer to Gitolite’s documentation: http://gitolite.com/		* “Gitolite” is used for hosting Git on this server. So for all the details, refer to Gitolite’s documentation: http://gitolite.com/
	* A quick tutorial about SSH public keys is here: http://git-scm.com/book/tr/v2/Git-on-the-Server-Generating-Your-SSH-Public-Key		* A quick tutorial about SSH public keys is here: http://git-scm.com/book/tr/v2/Git-on-the-Server-Generating-Your-SSH-Public-Key

Chris at 09:34, 8 November 2019

2019-11-08T09:34:47Z

← Older revision		Revision as of 09:34, 8 November 2019
Line 1:		Line 1:
	[[Category:~~version control~~]]		[[Category:misc-faq]]
	__TOC__		__TOC__

Heiko at 15:59, 15 March 2016

2016-03-15T15:59:46Z

← Older revision		Revision as of 15:59, 15 March 2016
Line 105:		Line 105:

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

	= Further information =		= Further information =

	* “Gitolite” is used for hosting git on this server. So for all the details, refer to Gitolite’s documentation: http://gitolite.com/		* “Gitolite” is used for hosting git on this server. So for all the details, refer to Gitolite’s documentation: http://gitolite.com/
	* A quick tutorial about SSH public keys is here: http://git-scm.com/book/tr/v2/Git-on-the-Server-Generating-Your-SSH-Public-Key		* A quick tutorial about SSH public keys is here: http://git-scm.com/book/tr/v2/Git-on-the-Server-Generating-Your-SSH-Public-Key

Heiko at 15:43, 15 March 2016

2016-03-15T15:43:17Z

← Older revision		Revision as of 15:43, 15 March 2016
Line 104:		Line 104:
	To list which roles are assigned for a repository, run the <code>perms</code> with the <code>-l</code> option command using SSH:		To list which roles are assigned for a repository, run the <code>perms</code> with the <code>-l</code> option command using SSH:

	<pre>ssh git@vcs.service.rug.nl perms -l abc/example</pre>		<pre>ssh git@vcs.service.rug.nl perms abc/example -l</pre>
	= Further information =		= Further information =

	* “Gitolite” is used for hosting git on this server. So for all the details, refer to Gitolite’s documentation: http://gitolite.com/		* “Gitolite” is used for hosting git on this server. So for all the details, refer to Gitolite’s documentation: http://gitolite.com/
	* A quick tutorial about SSH public keys is here: http://git-scm.com/book/tr/v2/Git-on-the-Server-Generating-Your-SSH-Public-Key		* A quick tutorial about SSH public keys is here: http://git-scm.com/book/tr/v2/Git-on-the-Server-Generating-Your-SSH-Public-Key

Heiko at 12:48, 12 January 2016

2016-01-12T12:48:38Z

Show changes

Heiko at 12:44, 12 January 2016

2016-01-12T12:44:06Z

Show changes

Heiko at 12:34, 12 January 2016

2016-01-12T12:34:09Z

← Older revision		Revision as of 12:34, 12 January 2016
Line 106:		Line 106:
	If more than one role is assigned, the role which allows the most will be in effect.		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 <code>perm -l</code> ~~command~~ using SSH:		To list which roles are assigned for a repository, run the <code>perm</code> command with the <code>-l</code> using SSH:

	<pre>ssh git@vcs.service.rug.nl perms -l abc/example</pre>		<pre>ssh git@vcs.service.rug.nl perms abc/example -l</pre>

	= Further information =		= Further information =

Heiko at 14:16, 7 October 2015

2015-10-07T14:16:57Z

← Older revision		Revision as of 14:16, 7 October 2015
Line 1:		Line 1:
			[[Category:version control]]
	__TOC__		__TOC__

Heiko at 13:42, 15 April 2015

2015-04-15T13:42:17Z

← Older revision		Revision as of 13:42, 15 April 2015
Line 17:		Line 17:
	; ''Directory name''		; ''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.		: 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 =		= Checking access =
Line 35:		Line 36:
	* You can read and write to a repository called <code>one/example</code>.		* You can read and write to a repository called <code>one/example</code>.
	* You can read the repository <code>doc</code>.		* You can read the repository <code>doc</code>.


	= Creating a repository =		= Creating a repository =
Line 53:		Line 55:

	When you create a repository, you will be registered as the owner of it. This enables you to grant access permissions to other persons.		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 =		= Granting access to others =
Line 73:		Line 76:

	<pre>ssh git@vcs.service.rug.nl perms abc/example - WRITERS john.doe@somehere.net</pre>		<pre>ssh git@vcs.service.rug.nl perms abc/example - WRITERS john.doe@somehere.net</pre>

	== Roles ==		== Roles ==

Line 104:		Line 108:

	<pre>ssh git@vcs.service.rug.nl perms -l abc/example</pre>		<pre>ssh git@vcs.service.rug.nl perms -l abc/example</pre>

	= Further information =		= Further information =

	* “Gitolite” is used for hosting git on this server. So for all the details, refer to Gitolite’s documentation: http://gitolite.com/		* “Gitolite” is used for hosting git on this server. So for all the details, refer to Gitolite’s documentation: http://gitolite.com/
	* A quick tutorial about SSH public keys is here: http://git-scm.com/book/tr/v2/Git-on-the-Server-Generating-Your-SSH-Public-Key		* A quick tutorial about SSH public keys is here: http://git-scm.com/book/tr/v2/Git-on-the-Server-Generating-Your-SSH-Public-Key

Heiko: Created page with "TOC 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..."

2015-04-15T13:28:47Z

Created page with "__TOC__ 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..."

New page

__TOC__

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, <code>@rug.nl</code> addresses are required.
; ''Your SSH public key''
: This is a small text file (~ 1kb). If you use OpenSSH, it is by default <code>~/.ssh/id_rsa.pub</code>. 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:

<pre>ssh git@vcs.service.rug.nl info</pre>
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:

<pre>C abc/..*
R W one/example
R doc</pre>
Which means:

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

= 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:

<pre>git clone git@vcs.service.rug.nl:abc/example</pre>
Breakdown of the URL:

; “git”
: The username for SSH. This is always “git”.
; “vcs.service.rug.nl”
: DNS name of the Version Control Server. This is always “vcs.service.rug.nl”.
; “abc”
: This is the directory where you can create repositories.
; “example”
: 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 <code>abc/example</code>, run the <code>perms</code> command using SSH like this:

<pre>ssh git@vcs.service.rug.nl perms abc/example + WRITERS john.doe@somehere.net</pre>
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 ‘-’:

<pre>ssh git@vcs.service.rug.nl perms abc/example - WRITERS john.doe@somehere.net</pre>
== Roles ==

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

; ''READERS''
: Only reading is allowed, i.e.:
;* clone
;* fetch
;* pull
; ''WRITERS''
: In addition to what READERS can do:
;* Fast-forward push (except to the “master” branch).
;* Create new branches.
;* Create tags.
; ''MASTERS''
: In addition to what WRITERS can do:
;* Fast-forward push to “master”.
; ''MANAGERS''
: In addition to what MASTERS can do:
;* Delete branches.
;* Delete tags.
;* Non fast-forward push, i.e. push amended commits, rebased or rewound branches.
; ''ADMINS''
: 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 <code>perm -l</code> command using SSH:

<pre>ssh git@vcs.service.rug.nl perms -l abc/example</pre>
= Further information =

* “Gitolite” is used for hosting git on this server. So for all the details, refer to Gitolite’s documentation: http://gitolite.com/
* A quick tutorial about SSH public keys is here: http://git-scm.com/book/tr/v2/Git-on-the-Server-Generating-Your-SSH-Public-Key