On 10/19/06, Frank Bille <[EMAIL PROTECTED]> wrote:
On 10/19/06, Upayavira <[EMAIL PROTECTED]> wrote:
>
> Option 3 would be possible, although you would be better asking for
> wicket.zones.apache.org (a Solaris zone) and running Joomla there - so
> that the source content is stored on Apache hardware.
>
That sounds like we can run Joomla on apache hardware on then forward
wicket.apache.org to that (so all is running on apache hardware)...
IIRC the Solaris zones are meant for experimental/testing stuff only -
Upayavira, do you know more? What I've seen is that the zones can be
restarted at any time without warning, resulting in (at least) a few
minutes downtime, lost sessions if you're editing, etc.
Over at Cocoon we're running the Daisy CMS on our zone
(http://cocoon.zones.apache.org/) to edit docs, and export them to
static files for publishing http://cocoon.apache.org. This is far from
ideal and slows down the site update cycle a lot, but it was the best
we could do at the time this was setup.
Other projects use the static pages for mostly static information, and
rely on their confluence wiki for the more dynamic information. This
might be the best compromise currently.
-Bertrand
