Question

So far from reading the git tutorails I have understood that for sharing my project files residing in my ubuntu linux server I need to create a bare repository and link it to the actual repository, so that when users clone the actual repo they get the actual repo having the actual work files.

And when they push their changes to the server the post-receive hook now updates the actual repo containing work files.

This is all I could understand and beyound that I have a lot of confusion for which I have the foll questions:

1) How do I create my bare repo.
2) How do I link it to the actual repo consisting the actual work files.
3) And what is this post-receive hook? Where does it reside? And what configurations do I need to do for the same.

Answer 1

How do I create my bare repo.

Read this.

To clone existing repository into a new bare repo, you would run this command:

git clone --bare my_project my_project.git

How do I link it to the actual repo consisting the actual work files.

Read this.

The non-bare repository can add the bare as a remote:

git remote add <name> <remote-URL>

Then, from the non-bare:

git push <name-of-remote> <branch-to-push-from>:<remote-branch-to-push-to>. 

Again, this is all covered in the Git SCM book, which I recommend you read before asking the same question again on StackOverflow.

Read the book. It gives you the terms to search for (such as git remote repositories, git bare server, etc). There are lots of questions on StackOverflow about this, when you know what to search for.

And what is this post-receive hook?

It’s a script that is run after the repository is pushed to. (After it has received data, the repository runs the post-receive script – sensible naming).

Where does it reside?

In the hooks directory of the bare repository; in .git/hooks otherwise. Read this.

And what configurations do I need to do for the same.

You do not need a post-receive hook to do what you’re asking to do (set up a basic bare repository so a small number of multiple users can git push and git pull from it). If you do not know what a hook is, you do not need one at this point. Set up your repository, get comfortable using basic git commands and working with collaborators on a bare repo, and ask a specific question about setting up and using a post-receive hook.

I can’t stress this enough: read the book. It will help. I learned a lot. 🙂 It will tell you how to:

1. How do I create my bare repo. (This is Chapter 4).
2. How do I link it to the actual repo consisting the actual work files. (This is Chapter 2, section 5).
3. And what is this post-receive hook? Where does it reside? And what configurations do I need to do for the same. (This is Chapter 7, section 3).