A Git server is simply an SSH server running the same Git application used on the client side.<\/p>\n
It is strongly recommended to use SSH keys when using SSH, especially when protecting company source code.<\/p>\n
If you have any doubts, read the post Setting Up SSH Keys<\/strong> [Link<\/a>].<\/p>\n Preparing the environment:<\/p>\n Switch to the new account:<\/p>\n Copy the public keys (\/home\/user1<\/span>\/.ssh\/id_rsa.pub<\/strong>) from all users who will be allowed to work with the repositories into the file \/home\/git\/.ssh\/authorized_keys<\/strong>, one per line.<\/p>\n At this point, follow the post Increasing Security with Fail2Ban<\/strong> [Link<\/a>] to protect SSH against brute force attacks.<\/p>\n Create repositories on the server:<\/p>\n Clone the remote repository locally:<\/p>\n Create a file and push it to the server:<\/p>\n The lines in gray are only needed the first time.<\/p>\n BONUS<\/strong><\/p>\n Automate Git operations across multiple repos simultaneously with MyRepos [Link<\/a>]. For example, pull all of them at once:<\/p>\nsudo apt update && sudo apt upgrade -y\r\nsudo apt install git -y\r\nsudo adduser git<\/pre>\n
su git\r\ncd ~\r\nmkdir .ssh\r\ntouch .ssh\/authorized_keys\r\nchmod 700 .ssh\r\nchmod 600 .ssh\/authorized_keys<\/pre>\n
ssh git@server\r\ngit init --bare repository1.git\r\nexit<\/pre>\n
git clone git@server:repository1.git<\/pre>\n
touch README.md\r\ngit add .\r\ngit config --global user.email \"user@example.com\"<\/span>\r\ngit config --global user.name \"Your Name\"<\/span>\r\ngit commit -m \"First Push\"\r\ngit push origin master<\/pre>\n
\nsudo apt install myrepos -y\r\ncd repositoryDirectory\r\nmr register\r\nmr run git pull<\/pre>\n