I noticed this too today, was last in on Wed PM and all the data was still there, but thought it was more website blocking from my work (lol, they block facebook, twitter, and google docs)...
Looking for community feedback:
In general, another item I thought about for the infra-working group is some sort of basic web site monitoring and site analytics for our main web site and community web site. I've used some 'pay for service' tools, but would be interested if anybody knows if any there are any other free, lightweight, and reliable solutions compatible with the technology stack, around this of the flavor:
1. of this can be provided as part of the EC2 services 'out of the box', (ie, our server stops responding and we can subscribe to sms messages. Or we can view and run site statistics based on usage)
2. something we could include into our lamp or RoR stacks 'easily' and 'openly' as extensions of this.
3. or, if we can leverage a SaaS type provider(s) for this similar to existing 'pay' tools (ie, http://internetsupervision.com/lp/IS.htm, http://www.pingdom.com/)
Of course, who they go to and what they do will have to be determined but I'd like to support a basic capability of this, in the 'future state' maintaining any of these site availability shouldn't be left to luck and chance just because we presume the services themselves to be fairly reliable, something can always happen...and you bring up another point, what are our assumptions about the backup (and possible recoverability) of the data if it were to be compromised at all because of some site failure? I know you lost stuff before, that was because of some 'admin' type mistake, but there is no guarantee this couldn't happen again. And for this one, I'd really like to understand if we can get to 'what was the failure' because we can ensure that if it was part of the crabgrass 'core design' that caused a site failure, that we open up a defect back to them...
Thanks,
Deborah
----- Original Message -----
From: "Sara Farmer" <sara....@btinternet.com>
To: crisis...@googlegroups.com, crisiscomm...@googlegroups.com
Sent: Friday, May 21, 2010 1:32:08 PM GMT -06:00 US/Canada Central
Subject: [CrisisCommons] CrabGrass unavailable?
I agree that having a "CrisisCommons" AMI is the best way to go. We
can have it configured with RoR, Postgresql, PHP and mod_python and
monitoring scripts. Monit & Nagios can "federate" together into a
single server for monitoring all the servers. I also get Twittered on
our server statuses
We use this at Fortius, so I'll ask our admin how much work it is to
replicate or what documentation he used and share with someone like
Elmer.
Andrew
--
Andrew Turner
mobile: 248.982.3609
and...@fortiusone.com
http://highearthorbit.com
http://geocommons.com Helping build the Geospatial Web
Introduction to Neogeography - http://oreilly.com/catalog/neogeography