Automatically keep a secondary repo in sync with a

问题:

We have a two tier setup.

We have a primary repository (called 'primary' below).

And a secondary repository (called 'secondary' below) that was created like so:

$ git clone --bare --shared $REPO_A/primary secondary.git

People working on the secondary repository view the branches which originated from the primary repository as read only but base their own branches off these branches.

We want to sync up the secondary repository with the primary repository once a day.

I.e. we want commits and new branches that were pushed to the primary to become visible to people working off the secondary repository (next time they do a pull).

We do not want this to be symmetric, i.e. activity against the secondary repository will not become visible to those working off the primary repository.

Ideally I'd like to run a cron job that runs on the machine with the bare secondary repository that somehow fetches new data from the primary and automatically includes it into the secondary.

I was hoping there might be a simple way to do this (and I'm hoping someone here will tell me there is).

If I were to write a script to do it, it would do:

• Create a fresh clone of the secondary.

  $ git clone $REPO_B/secondary
  $ cd secondary
  

• Get all its branches.

  $ git branch -r | sed 's?.*origin/??'
  

• Get all branches in the primary repo.

  $ git ls-remote --heads $REPO_A/primary | sed 's?.*refs/heads/??'
  

• For each primary branch for which I don't already have a corresponding secondary branch:

  $ git fetch $REPO_A/primary $BRANCHNAME:$BRANCHNAME
  $ git push origin $BRANCHNAME:refs/heads/$BRANCHNAME
  

• For each primary branch for which I already have a corresponding secondary branch:

  $ git checkout -b $BRANCHNAME --track origin/$BRANCHNAME
  $ git pull $REPO_A/primary $BRANCHNAME
  $ git push
  

As I'm new to git I wouldn't be surprised if I've failed to consider certain fundamental issues?

And like I said I'm hoping there's a simpler way of doing this, i.e. someone goes "oh, don't do all that, just do...".

回答1:

Oh, don't do all that, just do:

git --bare fetch

;)

(See this old thread for instance)
If you have added the relevant remote origins to your bare repo, you can fetch in turn each of those origins.

回答2:

You can just do a git clone --bare --mirror and periodically do a git fetch to make this happen.

I do it realtimish using a tool called gitmirror I wrote in node.js that I run on a machine at home to receive webhooks from github as well as ad-hoc hooks to sync up commits.

For a non-github example, I have a repo that's used for a couchdb backup that has a commit about once an hour. The cron job basically comes down to this:

# do some backup stuff
git commit -qam "Backup `date`" >> dump.log 2>&1

From there, I have a post-commit hook (.git/hooks/post-commit) that looks like this:

#!/bin/sh
curl -sS http://my.home.machine/gitmirror/bak/repo-name.git

You can accomplish the same thing by pushing from the receiving side. This has the advantage of firing-and-forgetting the payload in the normal case.