Return-Path: 
 <forrest-dev-return-2598-apmail-xml-forrest-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org
Received: (qmail 51134 invoked by uid 500); 9 Oct 2002 03:33:59 -0000
Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:forrest-dev-help@xml.apache.org>
list-unsubscribe: <mailto:forrest-dev-unsubscribe@xml.apache.org>
list-post: <mailto:forrest-dev@xml.apache.org>
Reply-To: forrest-dev@xml.apache.org
Delivered-To: mailing list forrest-dev@xml.apache.org
Received: (qmail 51123 invoked from network); 9 Oct 2002 03:33:57 -0000
Received: from new-smtp2.ihug.com.au (203.109.250.28)
  by daedalus.apache.org with SMTP; 9 Oct 2002 03:33:57 -0000
Received: from p24-max13.syd.ihug.com.au (expresso.localdomain)
 [203.173.155.216]
	by new-smtp2.ihug.com.au with esmtp (Exim 3.22 #1 (Debian))
	id 17z7bp-00072d-00; Wed, 09 Oct 2002 13:34:05 +1000
Received: from jeff by expresso.localdomain with local (Exim 3.35 #1 (Debian))
	id 17z7di-0000lP-00
	for <forrest-dev@xml.apache.org>; Wed, 09 Oct 2002 13:36:02 +1000
Date: Wed, 9 Oct 2002 13:36:02 +1000
From: Jeff Turner <jefft@apache.org>
To: forrest-dev@xml.apache.org
Subject: Re: [mini-RT] Using Forrest
Message-ID: <20021009033601.GA2724@expresso.localdomain>
Mail-Followup-To: forrest-dev@xml.apache.org
References: <20020911050656.GA1063@expresso.localdomain>
 <3DA34CA4.2080706@outerthought.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3DA34CA4.2080706@outerthought.org>
User-Agent: Mutt/1.4i
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
Status: O
X-Status: 
X-Keywords: 

On Tue, Oct 08, 2002 at 11:22:44PM +0200, Steven Noels wrote:
> Jeff Turner wrote:
> 
> >So I propose the existence of a new Forrest distribution, that embeds a
> >Tomcat 4 instance. There would be the following commands:
> >
> >forrest_startup.sh        # Start the embedded Tomcat
> >forrest_shutdown.sh       # Stop the embedded Tomcat
> >forrest_register.sh       # Register a project with Forrest
> >forrest_unregister.sh     # Unregister a project from Forrest
> >forrest_genstatic.sh      # Generate a static HTML version of the site
> >forrest_gendynamic.sh     # Generate a webapp version of the site
> >
> >The 'register' command would use Tomcat 4's Ant scripts [1] to deploy a
> >new webapp, without restarting Tomcat. The webapp would have it's context
> >root at the project root, not in ./build/, so that edits made to
> >src/documentation/* are immediately picked up, and files like status.xml
> >in the project root are inside the context.
> >
> >Does it all sound decent?
> 
> Hmmmm. Sounds tempting. Or should we provide just the scripts so that 
> people are able to deploy/update a Forrest instance running in their own 
> TC installation?
>
> Packaging TC seems like adding lots of weight to the distribution, IMO. 
> But abondoning static for live, and creating static using wget sounds 
> very tempting to me these days.

:) That's how I've been developing aft.sf.net for a long time now.

The major technical requirement is that Forrest must be able to act on a
project's 'native' directory structure, instead of requiring everything
to be copied into build/*. So when you edit
src/documentation/content/xdocs/index.xml, you can hit reload in your
browser and immediately see the change.

--Jeff


> Sorry for the very belated reply. I've been pretty busy.
> 
> </Steven>