Managing Remotes

booknest itself has no remote yet. git remote add <name> <url> creates one; add the server by path and, for the demonstration, a second name for it over SSH (Git's Transport Protocols):

git remote add origin ../server/booknest.git
git remote add backup ssh://dev@localhost:32022/home/dev/v5-ch2/server/booknest.git
git remote rename backup via-ssh
git remote -v
git remote remove via-ssh
git fetch origin
git branch -u origin/main

origin  ../server/booknest.git (fetch)
origin  ../server/booknest.git (push)
via-ssh ssh://dev@localhost:32022/home/dev/v5-ch2/server/booknest.git (fetch)
via-ssh ssh://dev@localhost:32022/home/dev/v5-ch2/server/booknest.git (push)
From ../server/booknest
 * [new branch]      main       -> origin/main
branch 'main' set up to track 'origin/main'.

Adding a remote contacts nothing; only the fetch does. rename and remove also rename or delete the remote-tracking branches, and git remote set-url origin <url> follows a server that moved. By convention origin is where you cloned from and upstream the project you forked. The last command gives main the upstream that git clone set up for the laptop.