Git: Why use a hook for setting up repo on your server?
Tutorial after tutorial on setting up a git repo on your server are essentially all the same — and they go like this:
- Install git on your server
git/project.gitoff your root directory of your server
git init --bare
- Add to post-receive:
#!/bin/bash\n 2 GIT_WORK_TREE=/path/to/your/vc'd/project git checkout -f
- Then make post-recieve executable:
chmod +x post-receive
- Back on your local machine,
git clone ssh://firstname.lastname@example.org/git/project.git
- And add files, commit and push
This is all fine, and I can indeed push to the
git/project.git and end up with those files in the
path/to/your/vc'd/project but I’m looking to understand…
Why use the hook at all?
It leaves you without the ability to pull your
path/to/your/vc'd/project/ on your local machine.
Why not just
git init the
clone it on your local machine?
Further, if anyone could explain how to get
git pull functionality on the local side for the
path/to/your/vc'd/project with this hooking method, it would be much appreciated
One Solution collect form web for “Git: Why use a hook for setting up repo on your server?”
It is best practice to push to a bare repo rather than a repo with a working tree.
That way, the user cannot be surprise to see the file pushed not be displayed, because the target repo would have one branch checked out and the user is pushing another branch.
Making the target repo update automatically a working tree based on what the user is pushing could be too dangerous: if you push the wrong branch, you replace your working tree content immediately.
This is different from pushing to a bare repo and updating an external working tree through a hook: you can do some control in said hook.
For more, see “all about “bare” repos — what, why, and how to fix a non-bare push”.