Re: kernel.org mirroring (Re: [GIT PULL] MMC update)
- From
- Jeff Garzik <jeff@garzik.org>
- Date
- Dec 9, 2006, 17:27 UTC
- Message-ID
- <457AF201.2000205@garzik.org>
- In-Reply-To
- <200612091802.12810.jnareb@gmail.com>
Jakub Narebski wrote:
Show 16 quoted lines
> Jeff Garzik wrote: >> Jakub Narebski wrote: > >>> As I said, I'm not talking (at least now) about saving generated HTML >>> output. This I think is better solved in caching engine like Squid can >>> be. Although even here some git specific can be of help: we can invalidate >>> cache on push, and we know that some results doesn't ever change (well, >>> with exception of changing output of gitweb). >> It depends on how creatively you think ;-) >> >> Consider generating static HTML files on each push, via a hook, for many >> of the toplevel files. The static HTML would then link to the CGI for >> further dynamic querying of the git database. > > You mean that the links in this pre-generated HTML would be to CGI > pages?
Yes, they must be. Otherwise, the gitweb interface changes.
You don't want to pre-generate HTML for every possible git query, that would cause an explosion of data.
Both the HTML generator and CGI would need to know which pages were pre-generated and which are not.
Jeff