Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Subject: Re: [zone] httpd configuration (was character entities)
From: Thorsten Scherler <thorsten@apache.org>
To: dev@forrest.apache.org
In-Reply-To: <20060128111735.GA6266@igg.indexgeo.com.au>
References: <1138137806.8230.48.camel@localhost.localdomain>
	 <20060124222311.GA5254@igg.indexgeo.com.au>
	 <1138142582.8230.66.camel@localhost.localdomain>
	 <1138194991.8219.96.camel@localhost>
	 <20060125221959.GA8058@igg.indexgeo.com.au>
	 <1138234705.8293.4.camel@localhost.localdomain>
	 <20060126011715.GA13242@igg.indexgeo.com.au>
	 <1138315795.8257.52.camel@localhost.localdomain>
	 <20060128060420.GA25489@igg.indexgeo.com.au>
	 <1138445095.8311.10.camel@localhost>
	 <20060128111735.GA6266@igg.indexgeo.com.au>
Content-Type: text/plain; charset=utf-8
Date: Thu, 02 Feb 2006 20:42:02 +0100
Message-Id: <1138909322.8351.183.camel@localhost>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit

El sáb, 28-01-2006 a las 22:17 +1100, David Crossley escribió: 
> Thorsten Scherler wrote:
> > David Crossley escribi??:
> > > 
> > > No need to have them all in SVN, just the one that
> > > we want to change.
> > > 
> > > I see that Cocoon put all their config into the
> > > pmc/cocoon section of the private committers svn.
> > 
> > Hmm, and how are they doing the checkout?
> 
> At the moment it is actually the other way around.
> They maintain the files on the server, and a tar-it-up.sh
> to gather the important files, then a committer unpacks
> and adds it to svn. A temporary measure.

Hmm, yeah a route that we should not go.

> 
> > I thought the private stuff is
> > with password and we cannot checkout stuff with a user on zones.
> 
> As long as the user is in the right group
> it will be fine. And as long as each user sets
> their umask properly.

Hmm, you know that svn stores the password in a file? This means at
least sudo can look up all passwords if she wants. I thought that was
the reason why we could not set up a forrestbot on zones that is
actually as well deploying to our website. ¿?

> 
> That module is private to "committers" so that
> should be okay.

Yeah, still the password is stored on the server.

> 
> > > We should do the same for sensitive files like httpd.conf
> > > 
> > > The main stuff would stay in our forrest/zones svn,
> > > because that is not sensitive and is of use to
> > > other people.
> > 
> > Agree but I am not sure how you thought about it.
> 
> Neither am i.

;-)

> 
> > > > > Either way, we will need a document to remind us of all about
> > > > > these specific symlinks and 'svn co'. I started something at
> > > > > f.a.o/zone.html
> > > > 
> > > > I have not checked it in yet because we should decide first whether we
> > > > want to have /etc/apache2/ in our svn or only /etc/apache2/httpd.conf.
> > > > 
> > > > I added it for now directly to /etc/apache2/httpd.conf and started the
> > > > server (which had been down).
> > > 
> > > Glad that more people can now start the services.
> > > We need to listen to infra@ and realise it is down.
> > 
> > Actually I submitted a patch to infrastructure to monitor lenya.zones
> > with http://monitoring.apache.org/status/
> > 
> > http://issues.apache.org/jira/browse/INFRA-698
> > 
> > If we want, I can do the same for forrest, then we know when it is down
> > and can react.
> 
> Our http server should only be down if the whole
> zones machine has been rebooted. So IMO no need
> for monitoring.

I have set up (again) a lenya instance on
http://lenya.zones.apache.org/index.html for us a while ago. I have not
told anyone till now because I hoped that my infra patch will be applied
and we could monitor the server right away. I did some testing with up
times and it seems to be fine this time.
http://lenya.zones.apache.org:9000/

But actually I would like to propose to set up a lenya instance on *our*
zones server (due to the fact that I am the only one in lenya ATM that
is looking out for the zone, it does not make any different to me to
support it directly here). I am keen that we slowly playing around with
lenya as cms and that we are independent from the lenya zone.

Further I would like to see as well a dynamic instance of forrest
running on zone (I plan to start a web gui for dynamically altering
structurer files) as show case.

> 
> > > Next step is to automate the startup. See the fixme
> > > note at http://forrest.apache.org/zone.html#admin
> > 
> > Yeah on lenya we seem to have it because you cannot stop the httpd
> > without another one get up instantly. I will try to find the difference
> > between both configs.
> 
> We don't have any config. As you can see we must start by
> hand after a reboot.
> 

I will try to set this up ASAP, since just today the server was down again (I started it again).

salu2
-- 
thorsten

"Together we stand, divided we fall!" 
Hey you (Pink Floyd)