On Wed, 2007-11-21 at 17:39 -0500, Bruce Momjian wrote:
> Stefan Kaltenbrunner wrote:
> > Tom Lane wrote:
> > > Stefan Kaltenbrunner <> writes:
> > >> Dave Page wrote:
> > >>> Ah - it only rebuilds the docs once a day. I thought we'd increased that
> > >>> frequency now wwwmaster is on a much faster box. I'm running the build
> > >>> manually now - the changes should be visible within an hour or so.
> > >
> > >> sounds like something we could easily do to reduce the turn-around times
> > >> for changes like this ...
> > >
> > > Given that most of the time the docs don't change from day to day,
> > > it seems like timed rebuilds are a waste of cycles. Can't it be
> > > set up with some kind of trigger arrangement? Or at least a quick
> > > check in the script to see if anything's changed?
> > yeah I was wondering if we maybe should do something similiar for
> > checkins to the pgweb repository in general (ie have a commit trigger a
> > rebuild) I'm not so sure how the doc building process works in detail to
> > see if that would be feasible.
> Uh, why not just point them to the developer docs?
developer.postgresql.org is frequently overloaded or just not
accessible. www.postgresql.org is distributed for performance and
redundancy. It also formats the docs "nicer" in the archives. And it has
docs searchable. The list goes on.. :-P