Where's the conventional place to store git repositories in a linux file system tree?
Solution 1:
There is no right or wrong answer here, except the one dictated by your own personal religion and the contents of the hier(7) manpage on your system.
typical Linux hier manpage ; typical BSD hier manpage)
/var/git/* seems reasonable to me personally. That's where I keep mine.
Solution 2:
Place it in a directory (or shared filesystem) under /srv. This is what it's for.
The /srv directory is intended for site-specific data served by the system. From the standard:
This main purpose of specifying this is so that users may find the location of the data files for particular service, and so that services which require a single tree for readonly data, writable data and scripts (such as cgi scripts) can be reasonably placed. Data that is only of interest to a specific user should go in that users' home directory.
The methodology used to name subdirectories of
/srvis unspecified as there is currently no consensus on how this should be done. One method for structuring data under/srvis by protocol, eg.ftp,rsync,www, andcvs. On large systems it can be useful to structure/srvby administrative context, such as/srv/physics/www,/srv/compsci/cvs, etc. This setup will differ from host to host. Therefore, no program should rely on a specific subdirectory structure of/srvexisting or data necessarily being stored in/srv. However/srvshould always exist on FHS compliant systems and should be used as the default location for such data.Distributions must take care not to remove locally placed files in these directories without administrator permission.
On an SELinux-enabled system, the default directory is /var/www/git, and repos should be in subdirectories thereof. Or, you can use, e.g. /srv/git and set the file context to be equivalent:
semanage fcontext -a -e /var/www/git /srv/git
Solution 3:
/home/git/
This might seem a bit unconventional at first but it is very reasonable as this directory is made for you (with correct permissions) when you do sudo useradd git. You can just switch to the git user, cd and immediately run:
$ mkdir .ssh; chmod 700 .ssh
$ touch .ssh/authorized_keys; chmod 600 .ssh/authorized_keys
and put public keys of your peers into the just created authorized_keys file.
After you git init --bare your project, the "url" is then just...wait for it...
git@<server>:<project>
Solution 4:
On my Arch Linux I have /srv/http for apache (which is system default) and I use it for my node.js http servers too. Similarly I decided to just put all git repositories in /srv/git.
I use GitLab, and /srv/git is the home folder for git in that case too.
Ultimately, it's up to you. I found that sticking to a format similar to other services in your distro is easy to remember.