access_sdf_gitea_using_ssh_keys
Differences
This shows you the differences between two versions of the page.
Next revisionBoth sides next revision | |||
access_sdf_gitea_using_ssh_keys [2022/01/27 01:16] – created from a bboard post by futurile peteyboy | access_sdf_gitea_using_ssh_keys [2022/02/07 21:32] – clarified some of the language about the server setup. jquah | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | I spent some time investigating and think I got to the bottom of it. | + | Futurile |
- | Useful information is that the gitea server (git.sdf.org) is hosted on ma.sdf.org. After you've created a user using the gitea web front-end, you can see that it exists | + | Useful information is that the gitea server (git.sdf.org) is hosted on ma.sdf.org. After your gitea account is created, it will reside |
- | - Create | + | - Create |
- | - Create a repository using the Gitea webapp. | + | - Login to the Gitea webapp |
- | - Upload a public ssh key using the Gitea webapp | + | - Upload a public ssh key using the Gitea webapp. |
- | * In then Gitea Web app go to Settings (top left) and then SSH/GPG Keys. In the Manage SSH Keys select 'Add Key' and upload a publich | + | * In then Gitea web app go to Settings (top right) and then SSH/GPG Keys. In the Manage SSH Keys select 'Add Key' and upload a public |
- | * Gitea manages the public SSH key *separately* from any other that you use to normally access ma.sdf.org. | + | * Gitea manages the public SSH key *separately* from any other that you use to normally access ma.sdf.org. |
* their existing ma.sdf.org public ssh key and they' | * their existing ma.sdf.org public ssh key and they' | ||
- | * generating | + | * a new key pair specifically for this gitea. Either of these is fine. |
- | - Check that public key authentication is working | + | - Check that public key authentication |
- | * The gitea server is running on the system as the ' | + | * The Gitea server is running on the system as the ' |
- | * The gitea server is running on port 2222, so we need to connect | + | * The Gitea server is running on port 2222, so our test of public key authentication will specify this port manually. (It is possible for the server |
- | * At the command line load the SSH key, using ssh-agent | + | * At the command line, test that your newly-uploaded SSH key is recognized by Gitea. A dedicated stanza for git.sdf.org in $HOME/ |
+ | < | ||
$ ssh -vvv git@git.sdf.org -p 2222</ | $ ssh -vvv git@git.sdf.org -p 2222</ | ||
* You'll see a load of output, if it's successful you'll see:< | * You'll see a load of output, if it's successful you'll see:< | ||
Line 20: | Line 21: | ||
debug1: Authentication succeeded (publickey). | debug1: Authentication succeeded (publickey). | ||
Authenticated to git.sdf.org ([205.166.94.33]: | Authenticated to git.sdf.org ([205.166.94.33]: | ||
- | | + | |
- Set up your repository one of two ways: | - Set up your repository one of two ways: | ||
- Use the repository via git | - Use the repository via git | ||
- | * In the gitea web page for the repository you created it shows you information about how to access | + | * The Gitea web page for any empty repository you create will show you the commands for accessing |
$ git pull git@git.sdf.org: | $ git pull git@git.sdf.org: | ||
$ git pull git@git.sdf.org: | $ git pull git@git.sdf.org: | ||
Line 31: | Line 32: | ||
$ git remote add upstream ssh:// | $ git remote add upstream ssh:// | ||
$ git push upstream master</ | $ git push upstream master</ | ||
- | * For my own reasons I've called the remote ' | + | * For my own reasons I've called the remote ' |
- Check output in gitea | - Check output in gitea | ||
- | * You should see output on the command-line, | + | * You should see output on the command-line, |
- | + | ||
- | -- Futurile | + |
access_sdf_gitea_using_ssh_keys.txt · Last modified: 2022/02/07 21:37 by jquah