cgit instead of gitweb?

[Mike McGrath]

On Fri, 30 Jul 2010, Mike McGrath wrote:

> On Fri, 30 Jul 2010, Simo Sorce wrote:
>
> > On Fri, 30 Jul 2010 09:01:47 -0500 (CDT)
> > Mike McGrath <mmcgrath at redhat.com> wrote:
> >
> > > On Fri, 30 Jul 2010, Orcan Ogetbil wrote:
> > >
> > > > On Fri, Jul 30, 2010 at 9:36 AM, Mike McGrath wrote:
> > > > > On Fri, 30 Jul 2010, Adam Jackson wrote:
> > > > >
> > > > >> On Fri, 2010-07-30 at 12:41 +0530, Rahul Sundaram wrote:
> > > > >> > Hi
> > > > >> >
> > > > >> > Any particular reason we are using gitweb at
> > > > >> > http://pkgs.fedoraproject.org/gitweb/.  Cgit is used in
> > > > >> > freedesktop.org is much more faster and resource efficient.
> > > > >>
> > > > >> With my fd.o hat on: Our experience with cgit hasn't been
> > > > >> completely trouble-free either, it seems to get stuck sometimes
> > > > >> feeding you old cached data.
> > > > >>
> > > > >> If we insist on running gitweb we should at least consider
> > > > >> running warthog's branch (the version that kernel.org uses):
> > > > >>
> > > > >> http://git.kernel.org/?p=git/warthog9/gitweb.git;a=summary
> > > > >>
> > > > >
> > > > > We are.
> > > > >
> > > >
> > > > When will this webpage be available? It is being loaded here since
> > > > last night. I have been told that the cgi is doing some caching. Any
> > > > progress report on this?
> > > >
> > >
> > > It is but the massive number of packages seems to be a problem.  We'll
> > > figure something out, for now just go to the package you're looking
> > > for:
> > >
> > > http://pkgs.fedoraproject.org/gitweb/?p=nagios.git
> > >
> > > 	-Mike
> >
> > Mike can't we just have a statically generated page for the root, and
> > there have links to the single packages, maybe in subpages divided by
> > groups, or alphabetically ?
> >
> > Yes, having the status of the repos on the first page is neat but not
> > worth killing the server for it.
> >
>
> That's one of the options we're looking at, actually one problem right now
> is cache isn't actually being generated.  We didn't realize this until
> people started hitting it (and we had the full package set on there).  So
> the looking continues.  I'll send updates as I get them.
>

K, this is all fixed now.  Well figured out at least.  Umask issue.  I'm
running a chmod now and it should be done soon?  An hour?  less?  We don't
really know but it's running now so at least the going to any specific
package should work.

Once that's done I'm going to re-evaluate the full package list.  We'll
have something for that soon.

	-Mike