Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 31798 invoked from network); 1 May 2005 20:08:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 1 May 2005 20:08:16 -0000 Received: (qmail 57282 invoked by uid 500); 1 May 2005 20:09:40 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 57217 invoked by uid 500); 1 May 2005 20:09:39 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 57200 invoked by uid 99); 1 May 2005 20:09:39 -0000 X-ASF-Spam-Status: No, hits=-10.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from minotaur.apache.org (HELO [127.0.0.1]) (209.237.227.194) by apache.org (qpsmtpd/0.28) with ESMTP; Sun, 01 May 2005 13:09:39 -0700 Message-ID: <4275372A.8070308@apache.org> Date: Sun, 01 May 2005 22:08:10 +0200 From: Torsten Schlabach User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: dev@forrest.apache.org Subject: Re: [RT] Serving Apache Forrest site from live Forrest References: <4272B45A.3070609@apache.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N > Apache is getting more hardware donated lately, so it may be that we > get to use it. In any case, I don't want to ask for the usage of it if > we don't yet know what to do with it, hence the RT. Before making the full move and serve the websites entirely dynamically, how about providing a Forrestbot infrastructure for projects to use in order for the generation of today's static sites to be server based. We in the Apache Lenya project each have to maintain our personal Forrest installation and generate the HTML locally in order to maintain our website, see: http://lenya.apache.org/community/website-update.html (This is painful, time consuming and error-prone IMO and experience.) I was looking at this issue some time ago and learned that there are no alternatives to this at that point in time because the ASF does not have a hardware to host a production Forrest(bot). Or is that available in the meanwhile and we just missed it? Regards, Torsten Nicola Ken Barozzi schrieb: > Ross Gardler wrote: > ... > >> Whilst I totally agree with the sentiment of this RT, can I ask one >> simple question before even starting on this discussion: >> >> Where will we be able to host a live version of Forrest? > > > Apache is getting more hardware donated lately, so it may be that we get > to use it. In any case, I don't want to ask for the usage of it if we > don't yet know what to do with it, hence the RT. >