2) To work on it locally.

3) It’s part of the hook.

Jeff, one question still remains, you refer “know setup the two hooks that I mention above” ….

I’m only seeing one hook. A post-update hook.

What am I missing?

Thanks again. It took 3 chapters on git pro book to answer those questions. :)

1) Why / Where should we do git remote rename origin ?

2) Why should we clone the Hub locally ? I thought that the bare hub repository would exist only on the shared host servers not locally.

3) On your hook mention above, is this line part of the hook (to be placed at the very end, or is it something else?)

exec git-update-server-infoThanks again, and sorry for all those questions. :(

git init --bare your Hub

git init your production directory
git commit your production dir
git remote add hub ~/site_hub.git to connect production to your Hubgit push hub master to push your production code into your HubDelete everything in your staging dirgit clone ~/site_hub.git into your staging dir to recreate your production site in staginggit remote rename origin hub to keep things sanegit branch staging && git checkout staging to create a new “staging” branch & check it outgit push hub staging to push your staging branch back to HubNow set up the two hooks like I mention above, and then clone the Hub locally, and push & pull into the two branches. Et voilà!

The original author here says:

“The first step is to initialize a new Git repository in the live web
site directory on the server, then to add and commit all the site’s
files.”

We have, here, two live directories, one for staging and another for production so, where should we this first step be made ?

Thank you all in advance.

add a README file or something to your ~/www (prime).