git post-receive checkout to remote machine?
If you add the following script as a
hooks/post-receive hook to a bare git repository
#!/bin/sh GIT_WORK_TREE=/bar git checkout -f
then whenever someone pushes to the repository the current state will be updated in directory
- rsync-filter commitable to git
- How to deploy from git repo without server having access to repo?
- Is Rsyncing git repo good enough backup solution?
- How to get git to use an ssh (rsh) transport other than “ssh”
- Convert .gitignore to rsync merge filter include file? (with sed or awk)
- rsync out of git repository or tar archive
foo.git to be on the same machine.
What’s the easiest way to modify it so that the checkout is made on a remote machine (say
One way would be to:
#!/bin/sh GIT_WORK_TREE=/tmp/bar git checkout -f rsync ... /tmp/bar baz:/bar
Is there a better way? Perhaps not requiring an intermediate temp directory? (If not what are the correct options to pass to rsync such that the resulting directory is indentical to being checked out directly?)
One Solution collect form web for “git post-receive checkout to remote machine?”
GIT_WORK_TREE=/bar means that
bar is a git repo.
bar is a git repo on the remote side, then it can pull from a bare repo
bare_bar.git (also on the remote side), to which you can push to.
In other words, your
post-receive hook would push to bare_bar repo through ssh, and a
post-receive hook on that bare repo would trigger the pull from the actual repo
bar: see “Creating a git repository from a production folder”.
I’d prefer a solution that keeps the remote server free of any .git dirs (and even the git package itself ideally)
In that case, your current post-receive hook and its
rsync command seems to be the only way to incrementally copy new data to a remote working tree.
git archivewould archive everything each time.
git bundlewould require git on the other side.