Go with Gogs. Just makes sure you _really need_ to host your own git repo and it's not some sort of overzealous security/compliance measure. If you don't trust

Go with Gogs. Just makes sure you _really need_ to host your own git repo and it's not some sort of overzealous security/compliance measure. If you don't trust github, gitlab, maybe sourcehut (https://sr.ht https://sr.ht - no affiliation) is a good fit? If you do setup an internal repo, makes sure you setup mirrors and/or remote backups and a documented and tested disaster recovery scenario. ps. if you don't need a web interface, a UNIX server running SSH is just fine. Server side: $ mkdir -p Projects/myeliteproject.git && cd Projects/myeliteproject.git $ git init --bare $ exit On the dev machine: $ mkdir -p Projects/myeliteproject.git && cd Projects/myeliteproject.git $ git init $ git remote add origin ssh://[user]@[hostname]/full/path/to/the/repo.git $ git push origin master $ echo "We need this commit in order to avoid errors" > first_commit.txt $ git add first_commit.txt $ git commit (write a reason here... "first needed commit" is a good one) $ git push $ git config branch.master.merge 'refs/heads/master' $ git config branch.master.remote origin $ git config --global push.default current (<em>This config is to avoid warning messages. Please read <a href="http://progit.org/book/ch9- 5.html">here</a> and consult documentation for refspecs</em>) $ git pull Already up-to-date. And if you need a web interface: https://git-scm.com/book/en/v2/Git-on-the-Server-GitWeb https://git-scm.com/book/en/v2/Git-on-the-Server-GitWeb :-)