I have an existing git environment set up like this:In order to deploy my changes to the production server, currently I:run git commit on the dev copyrun git push to send my changes to project.git, the central repositoryssh into the production serverrun git pull on the live copyI would like to eliminate steps 3 and 4 when pushing the master branch.  I have found multiple tutorials (like this one) on using the post-receive hook, but they all seem to assume that the bare repository will live on the production server, like this:In this scenario the live copy can be updated using post-receive by setting GIT_WORK_TREE to the correct local directory, and then running git checkout -f master.That's very slick, but it doesn't work with my existing environment.  I could always move my central repo from the development server to the production server, but I'm hoping there's some straightforward way to just notify the live copy to do a git pull automagically when the central repository receives a push.Any suggestions, or should I just bite the bullet and move the central repo to production?
After a bare git repo receives a push, can it notify a remote to pull?
git
ssh takes parameters of the command it should run so you can just create a hook that will run git pull on the remote server.ssh user@MachineB 'bash -s' < local_script.shor ssh user@machineB remote_cmd