First draft of gitea and ssh guide complete
This commit is contained in:
@@ -49,3 +49,4 @@ flycheck_*.el
|
||||
/network-security.data
|
||||
|
||||
|
||||
*.html
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 95 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 93 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 51 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 18 KiB |
@@ -1,36 +0,0 @@
|
||||
<?xml version="1.0" encoding="UTF-8" ?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
|
||||
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
|
||||
<html xmlns="http://www.w3.org/1999/xhtml">
|
||||
|
||||
<head>
|
||||
<title>gitea-ssh-setup.html</title>
|
||||
<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
|
||||
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<h1>Gitea ssh setup</h1>
|
||||
<p>This guide assumes you have registered and verified your account with an @RU.IS email address. If you have not setup your account yet, you must do that first.
|
||||
The gitea server at RU is on port 2222. <em>It does not respond on the usual port 22</em></p>
|
||||
<ul>
|
||||
<li><a href="https://docs.gitea.com/">Gitea Documentation</a></li>
|
||||
</ul>
|
||||
<h1>Installing ssh keys into Gitea</h1>
|
||||
<ol>
|
||||
<li>If you don't have an ssh key, generate one now following the guide on the (main ssh page)[index.md]</li>
|
||||
<li>Login to gitea.cs.ru.is</li>
|
||||
<li>Click on your user Icon on the top right and choose "Settings" in the dropdown</li>
|
||||
<li>On the Left, click on "SSH / GPG Keys"
|
||||
<img alt="menu of SSH / GPG Keys" src="Graphics/gitea-ssh-nokeys.png" /></li>
|
||||
<li>copy the contents of <code>~/.ssh/id_ed25519.pub</code> into the text box and click "Add Key". <em>On windows you can view it in Notepad to cut and paste it</em>.
|
||||
<img alt="SSH key pasted into the text field" src="Graphics/gitea-ssh-pubkey-paste.png" /></li>
|
||||
<li>It will then want you to verify the key by <strong>TODO</strong></li>
|
||||
</ol>
|
||||
<h1>Testing</h1>
|
||||
<p>If you have ssh setup properly with gitea, you should be able to test it this way:
|
||||
<img alt="ssh test result using git user: success" src="Graphics/gitea-cmdline-test-success.png" /></p>
|
||||
</body>
|
||||
</html>
|
||||
+10
-2
@@ -12,8 +12,16 @@ The gitea server at RU is on port 2222. *It does not respond on the usual port
|
||||

|
||||
1. copy the contents of `~/.ssh/id_ed25519.pub` into the text box and click "Add Key". *On windows you can view it in Notepad to cut and paste it*.
|
||||

|
||||
1. It will then want you to verify the key by **TODO**
|
||||
|
||||
1. It will then want you to verify the key by running a `ssh-keygen`. You will need to tell it where your public key is, typically `~/.ssh/id_ed25519.pub. **This process must be done quickly as the tokens expire!!!**
|
||||
1. First look at the validation information given. This guide assumes you are on linux of some sort, but there are directions for Windows also listed
|
||||

|
||||
2. Open a command shell (if you weren't already) and run the ssh-keygen command to sign the token with your key
|
||||

|
||||
2. Paste the results into the "Armored SSH signature" area
|
||||

|
||||
2. Click "Verify"
|
||||
1. If validation is done quickly and with the right key, you will see confirmation
|
||||

|
||||
|
||||
# Testing
|
||||
If you have ssh setup properly with gitea, you should be able to test it this way:
|
||||
|
||||
Reference in New Issue
Block a user