Git Protocols

Git Protocols:

Git can use four major network protocols to transfer data: Local, Secure Shell (SSH), Git, and HTTP.

Local Protocols:

The most basic is the Local protocol, in which the remote repository is in another directory on disk. This is often used if everyone on your team has access to a shared filesystem such as an NFS mount, or in the less likely case that everyone logs in to the same computer. We can make clone by these commands.

commands:

git clone /path_of_file/project.git
 or
git clone file:///path_of_file/project.git

SSH Protocols:

Probably the most common transport protocol for Git is SSH. This is because SSH access to servers is already set up in most places—and if it isn’t, it’s easy to do. SSH is also the only network-based protocol that you can easily read from and write to.

commands:

git clone ssh://root@server:project.git
 or
git clone root@server:project.git

Git Protocols:

This is a special daemon that comes packaged with Git; it listens on a dedicated port (9418) that provides a service similar to the SSH protocol, but with absolutely no authentication. In order for a repository to be served over the Git protocol.

commands:

git clone git@path_of _project:project.git

HTTP/s Protocols:

The beauty of the HTTP or HTTPS protocol is the simplicity of setting it up. Basically, all you have to do is put the bare Git repository under your HTTP document root and set up a specific post-receive hook

commands:

git clone http://example.com/project.git