- http://groups.google.com/group/daemon-kit (firstname.lastname@example.org)
- #daemon-kit on Freenode
Daemon Kit aims to simplify creating Ruby daemons by providing a sound application skeleton (through a generator), task specific generators (jabber bot, etc) and robust environment management code.
Using simple built-in generators it is easy to create evented and non-evented daemons that perform a multitude of different tasks.
- XMPP bot (evented)
- AMQP consumer (evented)
- SQS consumer
- Nanite agent (requires < 0.3)
- Cron-style daemon
- ruote remote participants
- Build it
- Review TODO.txt
$ daemon-kit -h
Get some help
$ daemon-kit [/path/to/your/daemon] [options]
The above command generates a skeleton daemon environment for you to adapt.
$ daemon-kit [/path/to/your/daemon] -i xmpp
Use the 'xmpp' generator instead of the default one.
Currently five generators exist: default, xmpp, amqp, cron, ruote. Prior to version 0.3 there was a nanite generator too.
The default generator creates a simple daemon with an infinite loop inside that you can adapt.
The jabber generator creates a simple daemon that leverages the blather gem to process inbound messages. The daemon will manage the roster and other little tasks, leaving you to provide the hooks for processing messages, presence notifications and subscription request.
The cron generator creates a simple daemon that leverages the rufus-scheduler gem to create a simple cron-like daemon. Please be aware that this daemon could never be a replacement for the battle-tested cron[http://www.gentoo.org/doc/en/cron-guide.xml] utility shipped standard with most *nix distributions.
The AMQP generator creates a simple daemon that has all the stub code and configuration in place to help you write AMQP consumers quickly and effectively. The generated daemon relies on the presence of the amqp gem.
The ruote remote participant generator speeds up the development of workflow participants that run outside of the Ruby process that houses the engine. Daemon-kit handles all the communication and delegation logic, allowing you to focus purely on your participant's activities.
- Ruby 1.8.7 or later (developed on REE/1.9.1)
- rspec (for writing/running your specs)
Depending on the generator you choose for your daemon, it might require additional gems to run.
- xmpp - blather ~> 0.8.7
- cron - rufus-scheduler (at least version 2.0.0)
- amqp - amqp
- ruote - none, although ruote should probably be running somewhere
The generators are all written using Thor, which is bundled with daemon-kit and not needed for running any of the generators.
Currently recommended to stick to the git repo:
$ git clone git://github.com/kennethkalmer/daemon-kit.git $ rake build $ gem install pkg/daemon-kit-X.X.X.gem
Stable versions, when released are available directly from Rubygems:
$ gem install daemon-kit
When upgrading daemons generated from earlier versions of daemon-kit, it is easier in most cases to re-generate the daemon. Since 0.1.8 the generators use Thor, which allows you to review a diff of each file before deciding to overwrite it.
(The MIT License)
Copyright (c) 2009 Kenneth Kalmer (Internet Exchange CC, Clear Planet Information Solutions Pty Ltd)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.