Git server is not but the SSH server and the same Git app used on the client-side.<\/p>\n
It is strongly recommended to use SSH-Keys while using SSH especially if it is protecting the source codes of the company.<\/p>\n
If you have any doubt read the post Setting Up SSH Keys<\/strong> [Link<\/a>].<\/p>\n Preparing the environment:<\/p>\n Change to the new account:<\/p>\n Copy the public keys (\/home\/user1<\/span>\/.ssh\/id_rsa.pub<\/strong>) from all the users that will be allowed to work with the repositories to the file \/home\/git\/.ssh\/authorized_keys<\/strong> each one in a different line.<\/p>\n At this point follow the post to Increasing Security with Fail2Ban<\/strong> [Link<\/a>] to protect the SSH against password brute force attacks.<\/p>\n Create the repositories inside the server:<\/p>\n Clone the remote repository to local:<\/p>\n Create a file and pull it to the server:<\/p>\n The lines in gray will only be used on the very first time.<\/p>\n BONUS<\/strong><\/p>\n Automate Git operations in multiple repos simultaneously with MyRepos [Link<\/a>]. For example, pull the all 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 Pull\"\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