1.7 KiB
| title | description | published | date | tags | editor | dateCreated |
|---|---|---|---|---|---|---|
| Setting Up Git | Steps to get up and running with Git | true | 2025-06-06T12:27:42.157Z | markdown | 2025-06-06T12:27:40.548Z |
Description:
Basic steps to get git connected to server and able to clone repos.
Steps:
- Install and configure git:
git config --global user.name "Your Name"
git config --global user.email "yourname@example.com"
git config --global init.defaultBranch main
git config --global color.ui auto
git config --global pull.rebase false
git config --global core.editor "code --wait"
- Create SSH Key
ssh-keygen -t ed25519
- Copy public key to server
cat ~/.ssh/id_ed25519.pub
- Clone desired repo using ssh
Notes:
In the even you rename the key to something other than id_rsa, add config file to .ssh folder
touch ~/.ssh/config then add:
Host github.com or git server
Hostname github.com
IdentityFile /path/to/privateKey
stat -c %a keyfile checks permissions of key if needed, must be 600
chmod 600 keyfile
Taken from this superuser thread:
Regarding contacting the same host with different keys: Here it is essential to understand that in
.ssh/config,Hostis a custom name you can give to the host specified underHostName. Thegithub.compart in the git URLgit@github.com:torvalds/linux.gitrefers to thisHostand thus has to match it exactly. If you have a second Github ssh key, you can create a sectionHost github2in~/.ssh/configand then use the URLgit@github2:torvalds/linux.g(see also superuser.com/a/1519694/96128). –user905686 Commented Apr 12, 2021 at 17:42