<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://wiki.flapjack-project.com/lib/exe/css.php?s=feed" type="text/css"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Flapjack Wiki</title>
    <subtitle></subtitle>
    <link rel="alternate" type="text/html" href="http://wiki.flapjack-project.com/"/>
    <id>http://wiki.flapjack-project.com/</id>
    <updated>2010-04-02T17:08:40+10:00</updated>
    <generator>FeedCreator 1.7.2-ppt DokuWiki</generator>
<link rel="self" type="application/atom+xml" href="http://wiki.flapjack-project.com/feed.php" />
    <entry>
        <title>installation_guides</title>
        <link rel="alternate" type="text/html" href="http://wiki.flapjack-project.com/installation_guides?rev=1269839191&amp;do=diff"/>
        <published>2010-03-29T15:06:31+10:00</published>
        <updated>2010-03-29T15:06:31+10:00</updated>
        <id>http://wiki.flapjack-project.com/installation_guides?rev=1269839191&amp;do=diff</id>
        <author>
            <name>Benjamin Krueger</name>
        </author>
        <summary>Installation guides


Currently, installing Flapjack is pretty ghetto. It's distributed as a RubyGem, and has a heavy set of dependencies. 

Native packages are in the works, so please bear with us until a less bongtastic install procedure is available.</summary>
    </entry>
    <entry>
        <title>packaging_guide</title>
        <link rel="alternate" type="text/html" href="http://wiki.flapjack-project.com/packaging_guide?rev=1259516684&amp;do=diff"/>
        <published>2009-11-30T04:44:44+10:00</published>
        <updated>2009-11-30T04:44:44+10:00</updated>
        <id>http://wiki.flapjack-project.com/packaging_guide?rev=1259516684&amp;do=diff</id>
        <author>
            <name>Lindsay Holmwood</name>
        </author>
        <summary>Packaging Guide


This document aims to comprehensively detail dependencies, build &amp; checkout processes, and recommendations for packaging Flapjack. 


Dependencies


Flapjack attempts to follow the Puppet route of keeping the number of dependencies very low. This reduces headaches for downstream packagers.</summary>
    </entry>
    <entry>
        <title>development_guides - created</title>
        <link rel="alternate" type="text/html" href="http://wiki.flapjack-project.com/development_guides?rev=1259451108&amp;do=diff"/>
        <published>2009-11-29T10:31:48+10:00</published>
        <updated>2009-11-29T10:31:48+10:00</updated>
        <id>http://wiki.flapjack-project.com/development_guides?rev=1259451108&amp;do=diff</id>
        <author>
            <name>Lindsay Holmwood</name>
        </author>
        <summary>Developing Flapjack

Testing


Flapjack is, and will always be, well tested. Monitoring is like continuous integration for production apps, so why shouldn't your monitoring system have tests?

Testing is done with rspec (spec/) and Cucumber (features/).</summary>
    </entry>
    <entry>
        <title>architecture - created</title>
        <link rel="alternate" type="text/html" href="http://wiki.flapjack-project.com/architecture?rev=1259450780&amp;do=diff"/>
        <published>2009-11-29T10:26:20+10:00</published>
        <updated>2009-11-29T10:26:20+10:00</updated>
        <id>http://wiki.flapjack-project.com/architecture?rev=1259450780&amp;do=diff</id>
        <author>
            <name>Lindsay Holmwood</name>
        </author>
        <summary>Flapjack's Architecture

Check lifecycle

	*  create check in admin interface
	*  clear jobs on beanstalkd
	*  run flapjack-populator
	*  check is run by flapjack-worker
		*  result is written onto beanstalkd
		*  check is written back on beanstalkd with a delay</summary>
    </entry>
    <entry>
        <title>start</title>
        <link rel="alternate" type="text/html" href="http://wiki.flapjack-project.com/start?rev=1259450492&amp;do=diff"/>
        <published>2009-11-29T10:21:32+10:00</published>
        <updated>2009-11-29T10:21:32+10:00</updated>
        <id>http://wiki.flapjack-project.com/start?rev=1259450492&amp;do=diff</id>
        <author>
            <name>Lindsay Holmwood</name>
        </author>
        <summary>*  Installation guides.
	*  Usage guides.
	*  Packaging guide.
	*  Development guides.
	*  Presentations.
	*  Flapjack's architecture.</summary>
    </entry>
    <entry>
        <title>usage_guides</title>
        <link rel="alternate" type="text/html" href="http://wiki.flapjack-project.com/usage_guides?rev=1259449787&amp;do=diff"/>
        <published>2009-11-29T10:09:47+10:00</published>
        <updated>2009-11-29T10:09:47+10:00</updated>
        <id>http://wiki.flapjack-project.com/usage_guides?rev=1259449787&amp;do=diff</id>
        <author>
            <name>Lindsay Holmwood</name>
        </author>
        <summary>Using Flapjack

Flapjack consists of several components that do one thing and do it well. This guide covers how each of the components work and interact with one another. 

Components

	*  flapjack-admin lets you configure checks through a web interface.
	*  flapjack-notifier notifies people if the check results are bad.
	*  flapjack-worker executes the checks and reports back results.
	*  beanstalkd is a work queue used to distribute checks and results.
	*  couchdb is a document-oriented databa…</summary>
    </entry>
</feed>
