Daniel BarkalowIs there a good way of handling a setup where the canonical repository is in some slow foreign system and you want a lot of git clones? I've been using a bare repository that I import into and clone, but then I need to go to the bare repository to update anything, which is vaguely annoying.
I remember people having my use case a while ago, and I was wondering if people have come up with improvements since.
-Daniel *This .sig left intentionally blank*
Sitaram ChamartyRe: Maintaining site-wide clones
On 2009-01-08, Daniel Barkalow <barkalow@iabervon.org> wrote:
> Is there a good way of handling a setup where the canonical repository is > in some slow foreign system and you want a lot of git clones? I've been > using a bare repository that I import into and clone, but then I need to > go to the bare repository to update anything, which is vaguely annoying.
Why? You can push to it too?
I don't have your use case but if I did, I'd do this: - everyone clones from the local mirror - one person clones the slow foreign system at whatever interval he thinks appropriate, and pushes to the local mirror - (or the local mirror can do this via cron)
This works fine if you can sort of judge the average frequency of updates, and not getting some of them *immediately* is not earth shattering for local developers.
If the slow foreign system lets you put in a post-commit hook that'll be even easier -- no more guesswork!