8 ways to share your git repository

See http://www.jedi.be/blog/2009/05/06/8-ways-to-share-your-git-repository/ for more detail.

Repository	Pros	Cons	Controlling Access	Create Repositories
File share	No network access required	Not internet friendly	Using filepermissions	Needs preparation per project on the share
Git daemon	Fast git protocol	Not internet friendly port	no good permission control. Read by default, Write can be enabled , but only anonymous	per project needs to be blessed
Plain SSH server	Allows good security	Not internet friendly port, requires account creation per user on server	Uses filepermissions	per project inited
SSH server git-shell	Enhancement of Plain SSH Server scenario	Not internet friendly port, requires account creation per user on server	Uses filepermissions	per project inited
Gitosis	Adds good remote management of users and repositories, only requires one system account	Not internet friendly port	Uses gitosis-config file	No server initalisation, only config is needed
Apache http	Falls back to standard apache config, only requires one system account, internet friendly	Slightly overhead	Uses htpasswd	per project inited
Apache http + gitweb	Falls back to standard apache config, only requires one system account, internet friendly, adds nice view of repository	Slightly overhead, read-only access	Uses htpasswd	per project inited
github	Internet accessible, easy to use webinterface	Hosted externally	Managing sshkeys	Web interface