Hey Guys,
Since we really wanted to have a live demo up and running of the java
sample container (so we can link to it from the getting started
guide), and it looks like it will take a little bit more time to
figure out how to proceed in such a way that infrastructure@ is happy
with running it (and backup facilities etc could be in place), i went
ahead and created a demo setup that we can use in the meantime at:
http://www.shindig-demo.org
The modules are rendered in the apps.shindig-modules.org domain, so
that we can give a good example of how that's supposed to work too.
Once the zone / hosting issues are worked out with the Apache
infrastructure team, i'll transfer the domains to the ASF.
-- Chris
On Jul 15, 2008, at 11:23 AM, Henning Schmiedehausen wrote:
On Tue, 2008-07-15 at 02:08 -0700, Kevin Brown wrote:
On Tue, Jul 15, 2008 at 1:46 AM, Chris Chabot <[EMAIL PROTECTED]>
wrote:
What I'm still very hopeful to see is a Wiki system (any
flavor will do) for Shindig.
The lack of documentation and possibilities for people to
contribute too- has really held our adoptation back a bit, and
caused many duplicate threads on the same subjects to happen.
On the other hand i remember infrastructure@ saying that a
zone should not be used for anything important?
Yeah, I'd be cautious about anything that needs to persist data on
the
zone.
That is not entirely correct. :-) Your zone will not suddenly vanish
or
being wiped. However, any substantial service for a project (e.g. a
doc
site, downloads, you name it) should at some point be migrated off a
zone and onto infrastructure proper. Zones are project-maintained and
running stuff off a zone means that there is e.g. no mirroring of
content available. Also, I'm not sure if Zones are backed up at all.
A zone is intended to run all the developer/committer related support
stuff like e.g. continuous build. It would be fine BTW to run a sample
container on the zone if you slap a .htaccess file on top of it (run
Apache in front of Tomcat) or request container authorization (with
straight Tomcat) and allow only committers/developers access to the
container.
The problem is scalability inside the Apache infrastructure, not
running
services. The zone machines are shared machines that don't serve for a
single project.
A hosted wiki would probably work. google sites might work ok for
this, though I still prefer something like MediaWiki in general.
Don't go there. We have two working Wiki infrastructures (Confluence
and
MoinMoin) and we have our very own JSPWiki in incubation if you feel
like setting up a Wiki on the Zone (which is fine, as long as only
committers have write access to it). I can understand infra to
object to
yet another wiki-flavor-of-the-day.
Ciao
Henning
