Hosting a Git Repo on Redbrick - Revision history

Graggle at 22:05, 21 April 2026

2026-04-21T22:05:12Z

← Older revision		Revision as of 22:05, 21 April 2026
Line 64:		Line 64:
	At this point you should do some work, like create a file and put something into it, or whatever. This is where a proper guide to git would be handy. Then commit your changes and do a first push:		At this point you should do some work, like create a file and put something into it, or whatever. This is where a proper guide to git would be handy. Then commit your changes and do a first push:

	git commit -a -m "~~My first~~ commit"		git commit -a -m "initial commit"
	git push origin master:refs/heads/master		git push origin master:refs/heads/master

Graggle at 22:04, 21 April 2026

2026-04-21T22:04:39Z

← Older revision		Revision as of 22:04, 21 April 2026
Line 70:		Line 70:

	[[Category:Helpdesk]]		[[Category:Helpdesk]]
			[[Category:Software]]

Graggle at 09:19, 21 April 2026

2026-04-21T09:19:39Z

← Older revision		Revision as of 09:19, 21 April 2026
Line 51:		Line 51:
	(the little ascii art bit might not show up on older versions of SSH).		(the little ascii art bit might not show up on older versions of SSH).

	This has created two files on your computer - id_ed25519 and id_ed25519.pub. id_25519 is your '''private''' SSH key, and id_ed25519.pub is the corresponding public key. You keep id_ed25519 to yourself, and you can give id_ed25519.pub to admins to allow you to access a repository. You can also upload it to a remote server (like redbrick) and put it in a specific location to allow you passwordless logins, which you can learn how to do at [[SSH-Keys]].		This has created two files on your computer - id_ed25519 and id_ed25519.pub. id_25519 is your '''private''' SSH key, and id_ed25519.pub is the corresponding public key. You keep id_ed25519 to yourself, and you can give id_ed25519.pub to admins to allow you to access a repository. You can also upload it to a remote server (like redbrick) and put it in a specific location to allow you passwordless logins, which you can learn how to do [[SSH-Keys\|here]].

Graggle at 09:19, 21 April 2026

2026-04-21T09:19:10Z

← Older revision		Revision as of 09:19, 21 April 2026
Line 68:		Line 68:

	''Things to look out for:'' When you're doing the "git remote add origin" command, make sure you add ".git" to the end of the repository name. The system that redbrick uses (called Forgejo, if anybody cares) to manage repositories needs that there. Also, in "git@git.redbrick.dcu.ie", the "git" user isn't a placeholder. You need use that user, not your own redbrick username.		''Things to look out for:'' When you're doing the "git remote add origin" command, make sure you add ".git" to the end of the repository name. The system that redbrick uses (called Forgejo, if anybody cares) to manage repositories needs that there. Also, in "git@git.redbrick.dcu.ie", the "git" user isn't a placeholder. You need use that user, not your own redbrick username.

			[[Category:Helpdesk]]

Graggle at 09:18, 21 April 2026

2026-04-21T09:18:53Z

← Older revision		Revision as of 09:18, 21 April 2026
Line 51:		Line 51:
	(the little ascii art bit might not show up on older versions of SSH).		(the little ascii art bit might not show up on older versions of SSH).

	This has created two files on your computer - id_ed25519 and id_ed25519.pub. id_25519 is your '''private''' SSH key, and ~~id_25519~~.pub is the corresponding public key. You keep ~~id_25519~~ to yourself, and you can give ~~id_25519~~.pub to admins to allow you to access a repository. You can also upload it to a remote server (like redbrick) and put it in a specific location to allow you passwordless logins, ~~but~~ you can ~~google for~~ how to do ~~that~~.		This has created two files on your computer - id_ed25519 and id_ed25519.pub. id_25519 is your '''private''' SSH key, and id_ed25519.pub is the corresponding public key. You keep id_ed25519 to yourself, and you can give id_ed25519.pub to admins to allow you to access a repository. You can also upload it to a remote server (like redbrick) and put it in a specific location to allow you passwordless logins, which you can learn how to do at [[SSH-Keys]].


Line 67:		Line 67:
	git push origin master:refs/heads/master		git push origin master:refs/heads/master

	''Things to look out for:'' When you're doing the "git remote add origin" command, make sure you add ".git" to the end of the repository name. The system that redbrick uses (called ~~Gitea~~, if anybody cares) to manage repositories needs that there. Also, in "git@git.redbrick.dcu.ie", the "git" user isn't a placeholder. You need use that user, not your own redbrick username.		''Things to look out for:'' When you're doing the "git remote add origin" command, make sure you add ".git" to the end of the repository name. The system that redbrick uses (called Forgejo, if anybody cares) to manage repositories needs that there. Also, in "git@git.redbrick.dcu.ie", the "git" user isn't a placeholder. You need use that user, not your own redbrick username.

Graggle at 19:54, 13 April 2026

2026-04-13T19:54:13Z

← Older revision		Revision as of 19:54, 13 April 2026
Line 20:		Line 20:
	To do this on a Unixey (Linux/Mac OS X/on redbrick) system, run:		To do this on a Unixey (Linux/Mac OS X/on redbrick) system, run:

	ssh-keygen -t ~~rsa~~		ssh-keygen -t ed25519 -b 2048

	You'll probably want to hit enter for most/all of the default options. Especially the first one (where to save the key). When it's done, you'll probably see something like this:		You'll probably want to hit enter for most/all of the default options. Especially the first one (where to save the key). When it's done, you'll probably see something like this:

	<pre>		<pre>
	[you@your-computer ~]$ ssh-keygen -t ~~rsa~~		[you@your-computer ~]$ ssh-keygen -t ed25519 -b 2048
	Generating public/private ~~rsa~~ key pair.		Generating public/private ed25519 key pair.
	Enter file in which to save the key (/~~Users~~/you/.ssh/~~id_rsa~~):		Enter file in which to save the key (/home/<you>/.ssh/id_ed25519):
	Enter passphrase (empty for no passphrase):		Enter passphrase (empty for no passphrase):
	Enter same passphrase again:		Enter same passphrase again:
	Your identification has been saved in /~~Users~~/you/.ssh/~~id_rsa.~~		Your identification has been saved in /home/<you>/.ssh/id_ed25519
	Your public key has been saved in /~~Users~~/you/.ssh/~~id_rsa~~.pub.		Your public key has been saved in /home/<you>/.ssh/id_ed25519.pub
	The key fingerprint is:		The key fingerprint is:
	58:~~06:86:0c:83:5e:4e:ab:75:93:96:37:76:42:73:07~~ you@your-computer~~.local~~		SHA256:nSZpii8CANduOS4PQ2hSM9ZgMUY3pdn1zAiLjCN902Q you@your-computer
	The key's randomart image is:		The key's randomart image is:
	+--[ ~~RSA 2048~~]----+		+--[ED25519 256]--+
	\| .oo .o E. \|		\| .B=o.E . \|
	\|. +o. + ~~. .~~ \|		\|.+*=oX + = \|
	\|. + . + ~~= .~~ \|		\|o=++B.+ . + \|
	\| . ~~+ * O~~ . \|		\|+o.o=. o . \|
	\| ~~o o =~~ S \|		\|+. o . S + \|
	\| . \|		\|. + .. o o \|
	\| \|		\| . =. . \|
	\| \|		\| . o. \|
	\| \|		\| . .. \|
	+----~~--------~~-----+		+----[SHA256]-----+
	[you@your-computer ~]$		[you@your-computer ~]$
	</pre>		</pre>
Line 51:		Line 51:
	(the little ascii art bit might not show up on older versions of SSH).		(the little ascii art bit might not show up on older versions of SSH).

	This has created two files on your computer - ~~id_rsa~~ and ~~id_rsa~~.pub. ~~id_rsa~~ is your '''private''' SSH key, and ~~id_rsa~~.pub is the corresponding public key. You keep ~~id_rsa~~ to yourself, and you can give ~~id_rsa~~.pub to admins to allow you to access a repository. You can also upload it to a remote server (like redbrick) and put it in a specific location to allow you passwordless logins, but you can google for how to do that.		This has created two files on your computer - id_ed25519 and id_ed25519.pub. id_25519 is your '''private''' SSH key, and id_25519.pub is the corresponding public key. You keep id_25519 to yourself, and you can give id_25519.pub to admins to allow you to access a repository. You can also upload it to a remote server (like redbrick) and put it in a specific location to allow you passwordless logins, but you can google for how to do that.

Digi at 20:54, 11 April 2026

2026-04-11T20:54:41Z

← Older revision		Revision as of 20:54, 11 April 2026
Line 5:		Line 5:
	== Getting a git repository on Redbrick ==		== Getting a git repository on Redbrick ==

	Redbrick hosts git repositories for users. You (and any other users you want) can have write access to the repositories. The world has read-only access via the web interface at [[http://git.redbrick.dcu.ie git.redbrick.dcu.ie]]. It's perfect for any small open source projects you feel like starting, or if you want to branch/fork an existing open source project that's hosted on git.		Redbrick hosts git repositories for users. You (and any other users you want) can have write access to the repositories. The world has read-only access via the web interface at [http://git.redbrick.dcu.ie git.redbrick.dcu.ie]. It's perfect for any small open source projects you feel like starting, or if you want to branch/fork an existing open source project that's hosted on git.

	=== Can I have a private repository that the world can't see? ===		=== Can I have a private repository that the world can't see? ===

Digi at 20:54, 11 April 2026

2026-04-11T20:54:24Z

← Older revision		Revision as of 20:54, 11 April 2026
Line 5:		Line 5:
	== Getting a git repository on Redbrick ==		== Getting a git repository on Redbrick ==

	Redbrick hosts git repositories for users. You (and any other users you want) can have write access to the repositories. The world has read-only access via the web interface at [[http://git.redbrick.dcu.ie]]. It's perfect for any small open source projects you feel like starting, or if you want to branch/fork an existing open source project that's hosted on git.		Redbrick hosts git repositories for users. You (and any other users you want) can have write access to the repositories. The world has read-only access via the web interface at [[http://git.redbrick.dcu.ie git.redbrick.dcu.ie]]. It's perfect for any small open source projects you feel like starting, or if you want to branch/fork an existing open source project that's hosted on git.

	=== Can I have a private repository that the world can't see? ===		=== Can I have a private repository that the world can't see? ===

Digi: Created page with "The beginners guide on how to use Git is here! Here's a badly written and terribly phrased guide on how to get and use a repository on redbrick's git hosting area. [https://git.redbrick.dcu.ie git.redbrick.dcu.ie] is currently not working. However, this guide will hopefully be of use when it is! == Getting a git repository on Redbrick == Redbrick hosts git repositories for users. You (and any other users you want) can have write access to the repositories. Th..."

2026-04-11T20:53:38Z

Created page with "The beginners guide on how to use Git is here! Here's a badly written and terribly phrased guide on how to get and use a repository on redbrick's git hosting area. [https://git.redbrick.dcu.ie git.redbrick.dcu.ie] is currently not working. However, this guide will hopefully be of use when it is! == Getting a git repository on Redbrick == Redbrick hosts git repositories for users. You (and any other users you want) can have write access to the repositories. Th..."

New page

The beginners guide on how to use Git is [[Git|here]]!
Here's a badly written and terribly phrased guide on how to get and use a repository on redbrick's git hosting area.
[https://git.redbrick.dcu.ie git.redbrick.dcu.ie] is currently not working. However, this guide will hopefully be of use when it is!

== Getting a git repository on Redbrick ==

Redbrick hosts git repositories for users. You (and any other users you want) can have write access to the repositories. The world has read-only access via the web interface at [[http://git.redbrick.dcu.ie]]. It's perfect for any small open source projects you feel like starting, or if you want to branch/fork an existing open source project that's hosted on git.

=== Can I have a private repository that the world can't see? ===
Yes any repository can be public or private.

=== Can I use this to host my third year/fourth year/other important college project? ===
Short answer: No. And you shouldn't do this in your redbrick home directory either. There have been a number of times in the past where Redbrick has experienced problems meaning that a user who had the only copy (or the only backup copy) of a project weren't able to access it at some important deadline.

Long answer: If you have other copies of your code, and Redbrick isn't the primary (only) backup of it, and you just wanted to have yet another backup of it "just because", then ''maybe'' it might make sense to put it on redbrick. But I still wouldn't.

=== Creating an SSH key pair ===
Before you can use redbrick's git repositories from one of your computers (or from your redbrick shell), you need to create a public/private SSH keypair there if you haven't already. You'll need to do this for every device/place that you want to access git from. This might sound annoying, but it also lets you use git without having to type a password every time you need to clone/push/pull.

To do this on a Unixey (Linux/Mac OS X/on redbrick) system, run:

ssh-keygen -t rsa

You'll probably want to hit enter for most/all of the default options. Especially the first one (where to save the key). When it's done, you'll probably see something like this:

<pre>
[you@your-computer ~]$ ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/you/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /Users/you/.ssh/id_rsa.
Your public key has been saved in /Users/you/.ssh/id_rsa.pub.
The key fingerprint is:
58:06:86:0c:83:5e:4e:ab:75:93:96:37:76:42:73:07 you@your-computer.local
The key's randomart image is:
+--[ RSA 2048]----+
| .oo .o E. |
|. +o. + . . |
|. + . + = . |
| . + * O . |
| o o = S |
| . |
| |
| |
| |
+-----------------+
[you@your-computer ~]$
</pre>

(the little ascii art bit might not show up on older versions of SSH).

This has created two files on your computer - id_rsa and id_rsa.pub. id_rsa is your '''private''' SSH key, and id_rsa.pub is the corresponding public key. You keep id_rsa to yourself, and you can give id_rsa.pub to admins to allow you to access a repository. You can also upload it to a remote server (like redbrick) and put it in a specific location to allow you passwordless logins, but you can google for how to do that.

=== Create the repository ===
Once the admins have done their work, you need to actually create the repository. You do this on your own computer (or redbrick account, or wherever one of your keys came from). If you asked the admins to create you a repository named "awesomeproject", you'd do the following:

mkdir awesomeproject
cd awesomeproject
git init
git remote add origin git@git.redbrick.dcu.ie:awesomeproject.git

At this point you should do some work, like create a file and put something into it, or whatever. This is where a proper guide to git would be handy. Then commit your changes and do a first push:

git commit -a -m "My first commit"
git push origin master:refs/heads/master

''Things to look out for:'' When you're doing the "git remote add origin" command, make sure you add ".git" to the end of the repository name. The system that redbrick uses (called Gitea, if anybody cares) to manage repositories needs that there. Also, in "git@git.redbrick.dcu.ie", the "git" user isn't a placeholder. You need use that user, not your own redbrick username.