Mailing-List: contact user-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@forrest.apache.org
Received-SPF: softfail (asf.osuosl.org: transitioning domain of
 webmaster@cfas.org does not designate 65.32.5.131 as permitted sender)
Message-ID: <42F00FB0.6080403@cfas.org>
Date: Tue, 02 Aug 2005 20:28:32 -0400
From: CFAS Webmaster <webmaster@cfas.org>
User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050723)
MIME-Version: 1.0
To: user@forrest.apache.org
Subject: Re: Help with new templates
References: <42ED7699.1060200@cfas.org>
 <200507312317.20420.diwaker@apache.org>  <42EEC320.6010507@cfas.org>
 <1122976071.7197.41.camel@localhost.localdomain> <42EFEB23.2030506@cfas.org>
 <1123023670.18215.8.camel@localhost.localdomain>
 <00c201c597b9$fe8aa450$0200a8c0@madaboutipv6>
In-Reply-To: <00c201c597b9$fe8aa450$0200a8c0@madaboutipv6>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Gav.... wrote:

>I was going to ask the question as I don't see it documented anywhere, how 
>does
>anyone publish a forrest site to the web so it is available to all.
>  
>
The way *I* do it is to run forrest from the root of the seeded tree, in 
my case in these emails it's .../cfas-new/, where you'll likely find the 
src/ directory. 

>I have an apache web server running so it is not a problem, just wondered if
>this project was meant for intranet use only or if porting to an ISP web 
>space
>was possible or a future goal.
>  
>
That's good.  What you'd want to do for a static site is give Apache 
access to the build/site directory under the seeded tree, eg. 
.../cfas-new/build/site/  There's probably an index.html file there that 
Apache will be happy to serve.

Another method is to copy the .../build/site/* tree into the web root of 
a server.

-Paul