Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1U66KX-0001LN-Sf for pgsql-www@arkaria.postgresql.org; Thu, 14 Feb 2013 21:26:58 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1U66KX-0005fC-4V for pgsql-www@arkaria.postgresql.org; Thu, 14 Feb 2013 21:26:57 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1U66KW-0005f7-OO for pgsql-www@postgresql.org; Thu, 14 Feb 2013 21:26:56 +0000 Received: from acidenitrix.villemain.org ([91.121.90.165]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1U66KU-0001Jf-Ew for pgsql-www@postgresql.org; Thu, 14 Feb 2013 21:26:56 +0000 Received: from [89.157.243.170] (helo=Dimitris-MacBook-Air.local) by acidenitrix.villemain.org with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1U66KS-00011H-1B; Thu, 14 Feb 2013 22:26:52 +0100 From: Dimitri Fontaine To: Magnus Hagander Cc: Dave Page , PostgreSQL WWW , Alvaro Herrera , Tom Lane Subject: Re: 403 - Forbidden on gitweb pages Organization: 2ndQuadrant References: <20314.1360801157@sss.pgh.pa.us> <20130214002454.GJ4546@alvh.no-ip.org> User-Mail-Address: dimitri@2ndQuadrant.fr Date: Thu, 14 Feb 2013 22:26:43 +0100 In-Reply-To: (Magnus Hagander's message of "Thu, 14 Feb 2013 05:24:59 +0100") Message-ID: User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.2 (darwin) MIME-Version: 1.0 Content-Type: text/plain X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-www Precedence: bulk Sender: pgsql-www-owner@postgresql.org Magnus Hagander writes: > The problem is basically that gitweb is a big perl cgi (yes, cgi only) > which means that for every request it had to reload all of perl and reparse > the whole script. And on top of that the actual implementation of several > features is fairly slow in itself. What about finding a more efficient replacement? http://gitlabhq.com/ http://hjemli.net/git/cgit/ We need to check that GitLab can be setup to not offer all of its features, and the CGIT way of displaying branches looks very much suited to our project back branches support. Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-www mailing list (pgsql-www@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www