On the remote machine I create a bare repository with the following command:
git init --bare $HOME/bare/My-Repo
On my local machine I clone a repo (but not the one that I have created on the remote machine):
git clone ssh://something.com/My-Repo
On my local machine, in the repository that I have just cloned, I create a "reference" to the above mentioned bare repository located on the remote machine:
git remote add my_remote ssh://remote.com/${USER}/bare/My-Repo
I do not know if it is relevant to my question but I also do the following stuff in my local repository:
git config remote.my_remote /some/path/git-receive-pack
git config remote.my_remote /some/path/git-upload-pack
Now, I can push from the local repository to the bare repository on the remote machine:
git push my_remote master
Now, the idea is that we create another repository on the remote machine which should take some content from the bare repository. I create this repo by executing something like this on the remote machine:
some_script.sh $HOME/bare/My-Repo $HOME/My-Repo
Now, I do some changes in the $HOME/My-Repo on the remote machine (please note that it is not the bare repository), then I git add and git commit and after that I push:
git push origin my-dev-branch
As a result I push to the bare repository (which is located on the same remote machine). After that I go to my local machine and "take" the changes from the remote machine (from the bare repository):
git fetch my_remote
git checkout -b my-dev-branch my_remote/my-dev-branch
git fetch origin
git rebase origin/master
So, my questions are: Why do we need this bare repository? Why can't we just have one remote repository and directly exchange content between the local and remote repositories? Or, alternatively, why can't we just rsync (or scp) the local repository to and from the remote machine?
ADDED
This is why I ask the question instead of googling. I have googled my question and the first link is here: http://www.saintsjd.com/2011/01/what-is-a-bare-git-repository/
I read there:
Repositories created with the git init command are called working directories. In the top level folder of the repository you will find two things: A .git subfolder with all the git related revision history of your repo A working tree, or checked out copies of your project files. Repositories created with git init --bare are called bare repos. They are structured a bit differently from working directories. First off, they contain no working or checked out copy of your source files. And second, bare repos store git revision history of your repo in the root folder of your repository instead of in a .git subfolder. Note… bare repositories are customarily given a .git extension.
So, now to understand that I need to know:
- What is "revision history"?
- What is "working tree"?
- What is "checked out copies"?
And this is just the first section. I know, that the response would be: Go and read the git tutorial or introduction to git. Well I did it. The first problem with it is that the use of terms is "circular". Term A is expressed through term B and term B is expressed through term A. Second, I do not have time to read a book just to find an answer on my question. Third, I am 100% sure that the answer on my question can be expressed in simple terms. It is actually trivial.
