We have a suggestion from Sam Ruby for how we could do this today:
Sam Ruby wrote:
> Things that exist on people.apache.org:/www/james.apache.org/ get
> rsynched to james.apache.org once an hour.
>
> Now, how do we get static html there? Well, a cron job with wget
> would do the trick. Doesn't matter if externally hosted roller
> generates the html statically or dynamically, all that matters is
> that it provides it in response to a get.
>
> Alternately, I have some code that can take one or more feeds and
> produce HTML from it. That code is well documented, but I'm even
> willing to set it up.
>
> Short term, either approach solves the immediate need, modulo some
> minor propagation delays. Doesn't require anybody to move any
> mountains. Doesn't put a strain on our infrastructure.
>
> Once in place, it can be optimized at our leisure. No "Make it
> happen!" fire drills required.
As I understand it, the gist of it seems to be that we'd have a generated
file based on our feed and a template we provide, and we'd pick up the
current feed content to merge with our static content. Sam will maintain
the "interesting" side for us until it can move to ASF Infrastructure, and
the public visible stuff will serve right off our site. I believe that he's
saying that the template which he will populate could be our main news page,
minus the news to be inserted into it. Periodically, we'd pick up a
potentially new copy containing the latest news merged into that page, which
would then be synched with the live site.
How would that work for everyone?
--- Noel
