From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael J Gruber Subject: Re: GIT smart http vs GIT over ssh Date: Tue, 31 Jul 2012 11:20:40 +0200 Message-ID: <5017A368.3010501@drmicha.warpmail.net> References: <20120731031011.GA1685@localhost.localdomain> <50179B89.4050106@drmicha.warpmail.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Konstantin Khomoutov , git@vger.kernel.org To: vishwajeet singh X-From: git-owner@vger.kernel.org Tue Jul 31 11:20:49 2012 Return-path: Envelope-to: gcvg-git-2@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Sw8dD-00028j-Vt for gcvg-git-2@plane.gmane.org; Tue, 31 Jul 2012 11:20:48 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753900Ab2GaJUn (ORCPT ); Tue, 31 Jul 2012 05:20:43 -0400 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:59006 "EHLO out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753452Ab2GaJUm (ORCPT ); Tue, 31 Jul 2012 05:20:42 -0400 Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 1CF9C20DEF; Tue, 31 Jul 2012 05:20:42 -0400 (EDT) Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 31 Jul 2012 05:20:42 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=lDVrk9en4FFUzqFSI9mQMV h00JM=; b=AdbnB+B8ZM131kdNMpJA3x5mH8eFC/ggG0a+KiVnXj+i5KShOma79z mA6qU4IP/2n8bSBZz1IcJ7QFl7mJskwWcp7svUiTLrHHh0jhFF8LphGJsD2LTfdi CySrNlxIcE4RKyJfeAOPIhMTgnNgJN7Kb2i6h3jKgg0/5NB2vUBK8= X-Sasl-enc: QwtUv5MR3ShNFMWKL6XeDboQr0TX5QBWrFuxxu33FPpY 1343726441 Received: from localhost.localdomain (unknown [130.75.46.56]) by mail.messagingengine.com (Postfix) with ESMTPA id 6A89B4835FE; Tue, 31 Jul 2012 05:20:41 -0400 (EDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120717 Thunderbird/14.0 In-Reply-To: Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: vishwajeet singh venit, vidit, dixit 31.07.2012 11:04: > On Tue, Jul 31, 2012 at 2:17 PM, Michael J Gruber > wrote: >> vishwajeet singh venit, vidit, dixit 31.07.2012 05:19: >>> On Tue, Jul 31, 2012 at 8:40 AM, Konstantin Khomoutov >>> wrote: >>>> On Tue, Jul 31, 2012 at 08:36:07AM +0530, vishwajeet singh wrote: >>>> >>>>> Just wanted to know the difference between smart http and ssh and in >>>>> what scenarios we need them >>>>> I am setting up a git server, can I just do with smart http support >>>>> or I need to enable the ssh support to use git effectively. >>>>> As I understand github provides both the protocols, what's the reason >>>>> for supporting both protocols. >>>> http://git-scm.com/book/en/Git-on-the-Server-The-Protocols >>>> http://git-scm.com/2010/03/04/smart-http.html >>>> >>> >>> Thanks for the links, I have already gone through those links, was >>> looking from implementation perspective do I really need to support >>> both protocols on my server or I can just do with smart http and >>> what's the preferred way of doing it smart http or ssh >>> >>> >> >> You need to provide what your users demand ;) >> >> Seriously, this is why GitHub and other providers offer both. Not only >> are some users more comfortable with one protocol or the other (Win >> users don't prefer ssh generally) but some might be able to use only one >> because of firewalls or corporate rules. >> >> From the server perspective, the setup is completely different, of >> course. Do you have shell accounts already which you want to reuse for >> ssh+git? Do you prefer setting up a special purpose shell account >> (gitosis/gitolite) or setting up a web server with authentication? >> > I already have server setup with smart http backend, was just > wondering if my users would really need ssh support or not and I agree > to your point it should be based on user demand. > > While going through the git book I encountered a very tall claim about > smart http > " I think this will become the standard Git protocol in the very near > future. I believe this because it's both efficient and can be run > either secure and authenticated (https) or open and unauthenticated > (http). It also has the huge advantage that most firewalls have those > ports (80 and 443) open already and normal users don't have to deal > with ssh-keygen and the like. Once most clients have updated to at > least v1.6.6, http will have a big place in the Git world." > > http://git-scm.com/2010/03/04/smart-http.html > > Just based on above comment in book I thought if smart http is way to > go for future why to take hassle of setting up ssh. There is no need to set up ssh if smart http does the job for you. I don't think it makes a difference performance-wise on the server (upload-pack vs. http-backend) but others are more proficient in this area. I'm sure ssh+git is there to stay, it is just ordinary anonymous git protocol tunneled through ssh. So, it's as future-proof as git is. > I was planning to use gitosis as I have python background and code > looks not being maintained from quite sometime, which worries me a > bit, I stumbled upon gitomatic > https://github.com/jorgeecardona/gitomatic, has anyone any prior > experience No idea about gitomatic. It looks a bit like "gitolite in python" (alpha) but doesn't say much about it's ancestry. There's also gitolite which is actively maintained and used. Basically, it's "gitosis in perl". Sitaram, forgive me ;) Michael