Re: New to git
- From
- Marco Maggesi <marco.maggesi@gmail.com>
- Date
- Apr 9, 2011, 19:15 UTC
- Message-ID
- <BANLkTikCF7Kv2xVYmr3O_P2t1TAzEFxXiA@mail.gmail.com>
- In-Reply-To
- <20110408201024.GA15964@sigill.intra.peff.net>
Hi Chris and Peff,
2011/4/8 Jeff King <peff@peff.net>:
Show 13 quoted lines
> But if you are just using the server as a distribution point for a > single repository, it can be much simpler. For example, if you always > just want to push and overwrite what is on the server (i.e., like a > mirror), you can just use plain rsync outside of git. To avoid mirror > lag, you do want to update the objects before the refs. So this: > > LOCAL=/path/to/repo.git > REMOTE=server:path/to/repo.git > rsync -a $LOCAL/objects/ $REMOTE/objects/ > rsync -a $LOCAL $REMOTE > > would work. And then expose repo.git on the server via http or ftp, and > clients can clone directly from it.
this is the solution I was looking for (but I where not sure that it worked).
> You didn't list your reasons, so I'll assume they're good. But note that > you don't need to be the administrator to accept a git push. You can > build it as a regular user, and have git connect over ssh and run the > server side.
Well, the server is a very old machine and I didn't find easy to compile git on it because of many missing dependencies (but I didn't try very hard either). A better solution would be to upgrade the server. But your solution is perfect meanwhile.
Thank you, Marco