From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dave Page <dpage(at)postgresql(dot)org>, pgsql-www(at)postgresql(dot)org |
Subject: | Re: Out-of-date 8.3 beta docs |
Date: | 2007-11-21 22:39:17 |
Message-ID: | 200711212239.lALMdHV14008@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
Stefan Kaltenbrunner wrote:
> Tom Lane wrote:
> > Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> 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?
http://developer.postgresql.org/pgdocs/postgres/index.html
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas 'ads' Scherbaum | 2007-11-22 01:52:29 | Re: [pgsql-eu-general] an admin team for the new European servers |
Previous Message | Stefan Kaltenbrunner | 2007-11-21 19:51:44 | Re: Out-of-date 8.3 beta docs |