Re: Is git over http (git-http-push) ready for production ?
- From
- Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
- Date
- Feb 19, 2010, 14:04 UTC
- Message-ID
- <20100219140419.GB31796@Knoppix>
- In-Reply-To
- <hllp07$o78$1@ger.gmane.org>
On Fri, Feb 19, 2010 at 11:26:16AM +0100, Fabien wrote:
Show 5 quoted lines
> Hi, > > Following my last email about locks problem with reiserfs (see > git-http-push (git v1.5) problems with DAVLockDB on reiserfs FS), I was > wondering how reliable is git-http-push.
Show 5 quoted lines
> Another problem I see is the password in clear text in ~/.netrc to avoid > to type passwords all the time. > > Finally, hooks don't work when using git over http (yep, I know, it's a > "dumb" protocol)...
1.6.6 introduced Smart HTTP. It is much more efficient, can run hooks and has same kind of atomicity guarantees as ssh://, but it has few shorcomings:
- Requires server support (CGI script & Git 1.6.6+) - Hook messages don't work (at least with 1.6.6.X/1.7.0.X) - Requires 1.6.6+ on client side - Authentication still sucks (no surprise, auth with HTTP just plain sucks).
But I regard HTTP fetch/push as backup for cases where git:// and ssh:// are not possible.
-Ilari