incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <>
Subject Re: website apache clerezza
Date Wed, 16 Mar 2011 20:28:24 GMT
Just be warned that the ASF infrastructure team do not support a wide 
range of solutions for managing Apache websites. The main reason is that 
they have to make sure our servers stay up and running and you'd be 
surprised at the load placed on them and the security requirements we have.

The basic rule is that the content must be statically served from ASF 
servers and that content must be placed in SVN to allow infra to do 
their "magic".

The ASF provides simple CMS system for creating websites. I'd describe 
this as bare bones, but functional. It allows for online and offline 
(via subversion) editing. There are also a number of tools for 
generating the static content from other sources.

When it comes time to consider the publication chain your mentors will 
tell you more.


On 16/03/2011 19:53, Marco Zaugg wrote:
> Good idea. We could even go using the open-sourced web content management system
> 'Trialox CMS' which is based on Apache Clerezza.
> But I'd suggest to first focus on the content of the website instead of spending
> too much time in create the pages dynamically. The current site on
> is simply too bad (and it's still having this nasty typo at the beginning of the
> page 'ApachClerezza').
> -----Original Message-----
> From: [] On Behalf Of Reto Bachmann-Gmuer
> Sent: Mittwoch, 16. März 2011 20:44
> To:
> Cc: Tsuyoshi Ito; Dirk Dresch
> Subject: Re: website apache clerezza
> Hi Tsuy
> I see no reason not to eat our own dogfood and create the website using
> Clerezza as we're currently doing.
> Reto
> On Wed, Mar 16, 2011 at 5:08 PM, Tsuyoshi Ito<>  wrote:
>> Hi
>> I am working on the html prototype of the clerezza website. I want to
>> ask if somebody knows if there are any best practices on how to
>> deploy/maintain an apache website (xsite?). IMO most of the website
>> content is static and therefore does not have to be created
>> dynamically. Probably we have a news section and a download section
>> which should be generated dynamically (via continuous  integration
>> server) or feeded from our demo server.
>> However a first prototype is available under
>> feedback is welcome (
>> cheers
>> tsuy

View raw message