| From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Dave Page <dpage(at)pgadmin(dot)org>, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: 403 - Forbidden on gitweb pages |
| Date: | 2013-02-14 21:26:43 |
| Message-ID: | m2r4kiziwc.fsf@2ndQuadrant.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
Magnus Hagander <magnus(at)hagander(dot)net> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stefan Kaltenbrunner | 2013-02-14 21:53:59 | Re: 403 - Forbidden on gitweb pages |
| Previous Message | Stefan Kaltenbrunner | 2013-02-14 21:14:20 | Re: azpug@postgresql.org |