Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 11460 invoked from network); 21 Aug 2007 09:47:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Aug 2007 09:47:26 -0000 Received: (qmail 14988 invoked by uid 500); 21 Aug 2007 09:47:23 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 14942 invoked by uid 500); 21 Aug 2007 09:47:23 -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 List-Id: Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 14931 invoked by uid 99); 21 Aug 2007 09:47:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Aug 2007 02:47:23 -0700 X-ASF-Spam-Status: No, hits=2.7 required=10.0 tests=SPF_NEUTRAL,WEIRD_PORT,WHOIS_NETSOLPR X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [129.67.1.171] (HELO relay8.mail.ox.ac.uk) (129.67.1.171) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Aug 2007 09:47:51 +0000 Received: from smtp1.mail.ox.ac.uk ([129.67.1.207]) by relay8.mail.ox.ac.uk with esmtp (Exim 4.67) (envelope-from ) id 1INQK9-0006Ax-RU for dev@forrest.apache.org; Tue, 21 Aug 2007 10:46:57 +0100 Received: from oucs-rossg.oucs.ox.ac.uk ([129.67.101.125]) by smtp1.mail.ox.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1INQK9-0006zn-4U for dev@forrest.apache.org; Tue, 21 Aug 2007 10:46:57 +0100 Message-ID: <46CAB490.2030402@apache.org> Date: Tue, 21 Aug 2007 10:46:56 +0100 From: Ross Gardler User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: dev@forrest.apache.org Subject: Re: multiple projects in single forrest instance References: <46C1B078.1080209@kraftfeld.org> <46C1CCF8.9050808@apache.org> <46C1D3FA.4050504@kraftfeld.org> <46C43799.70604@apache.org> <499888440708160453w290a0f28od745e550f98f3073@mail.gmail.com> <46C44D18.7060508@apache.org> <46C771A1.3050901@kraftfeld.org> <46C7F50B.2010005@apache.org> <46C854CE.60800@kraftfeld.org> <46C8C165.7010208@apache.org> <46CA2630.3070000@kraftfeld.org> In-Reply-To: <46CA2630.3070000@kraftfeld.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Oxford-Username: oucs0040 X-Virus-Checked: Checked by ClamAV on apache.org llamar burgess wrote: > Ross Gardler schrieb: >> One question whilst you are working on this - how is your site >> URLspace going to be structured? Will it be: >> >> http://foo.org/Site A/index.html >> http://foo.org/Site B/index.html >> http://foo.org/Site B/index.html .. > Thats exactly how i wanted it to be. > Whats next? :] I've built a simple test site that does the first stage of this. If you could follow along with your test site then we can be sure it works. As your understanding of the way Forrest works you'll be able to add functionality to the test site. In the meantime, please ask questions, add requirements to the list at the start of the index doc (see below) and do whatever else you think may help us move this forwards. STATUS ====== All I've done so far is create a proof of concept, it is a very long way from complete. Do the following: cd FORREST_HOME svn up cd whiteboard/multipleSites/master Edit forrest.properties.xml by changing the value of the property below to reflect your filesystem: Now do: forrest run http://localhost:8888 The resulting page tells you a bit about what I have done in this "multipleSites" experiment in whiteboard. If you want quick motivation then request: http://localhost:8888/seed/index.html What you are now looking at is the index page from multipleSites/subsite-seed - but not you ran forrest in the multipleSites/master Now go back and read http://localhost:8888 properly, test it out on your test site and supply a patch including any clarifications/additions to the content of the instructions. Also add any requirements you would like to that page. Then tell me it works/does not work and identify what we need to work on next - there are lots of holes in this at present but since you have the real world use case I'd rather you pointed at which hole to fill first. Ross