apphunkd 0.9.0

data/vendor/daemon-kit/Logging.txt

@@ -0,0 +1,92 @@
+= Logging from inside your daemon
+
+Proper logging inside your daemon process is critical, and daemon-kit
+provides you with a great logging facility to (ab)use.
+
+== Logging examples
+
+From anywhere in your code you can access the
+<em>DaemonKit.logger</em> instance, which is a configured
+DaemonKit::AbstractLogger. It is compatible with Ruby's Logger class
+but is much more verbose to help you gain some insight into your
+running process.
+
+  DaemonKit.logger.info( "Hello world" )
+
+This logs a 'Hello world' line to the log file, complete with the
+calling file name and line number. Log lines look something like this:
+
+  2009-06-07 23:21:30.248575 capd(32513) [INFO] initializer.rb:91: DaemonKit (0.1.7.4) booted, now running capd
+
+Log as much as you can, but be careful not to abuse the <em>info</em>
+level since your log files can become huge. For general processing
+hints, use the <em>debug</em> level.
+
+To log exceptions, use the special <em>exception</em> helper:
+
+  begin
+    # dangerous operation
+  rescue => e
+    DaemonKit.logger.exception( e )
+  end
+
+== Controlling logging in a running process
+
+Logging can be controlled in a running process, either via code or by
+sending UNIX signals to the running process.
+
+=== Changing log levels in your code
+
+Log levels can be toggled with the <em>level=</em> method:
+
+  DaemonKit.logger.level = :info
+
+Alternatively you can silence all the logging activity for a while
+using the silence helper:
+
+  DaemonKit.logger.silence do |logger|
+    # logger will only report :error or higher levels
+  end
+
+=== Changing log levels via UNIX signals
+
+Send your process the +USR1+ signal to toggle between <em>:debug</em>
+and <em>:info</em> log levels. Sending a +USR2+ signal will force the
+logger into <em>:debug</em> mode (+USR1+ will revert).
+
+== Support for log rotation
+
+Support for logrotate is baked right into daemon-kit. By sending your
+daemon a +HUP+ signal all the log files file be closed and re-opened
+again on first use. Here is an example logrotate configuration:
+
+  /path/to/daemon.log {
+    rotate 5
+    weekly
+    postrotate
+      kill -HUP `cat /path/to/daemon.pid`
+    endscript
+  }
+
+== Support for syslog logging
+
+If you have the
+SyslogLogger[http://seattlerb.rubyforge.org/SyslogLogger/] gem
+installed, you can have your process log to a UNIX syslog server. You
+can change the logging to syslog by either updating your
+<em>environment.rb</em> file like this:
+
+  config.log_path = :syslog
+
+Or by passing 'syslog' as the logfile argument when starting a daemon
+
+  $ ruby ./bin/daemon start -l syslog
+
+The SyslogLogger rdoc's provide configuration examples for configuring
+various UNIX syslog servers.
+
+== More logging information
+
+If you're running your daemon in the foreground (with the <em>run</em>
+command, you'll get copies of all the log messages on STDOUT, and thus
+voiding the need to tail log files the whole time.

data/vendor/daemon-kit/Manifest.txt

@@ -0,0 +1,166 @@
+Configuration.txt
+Deployment.txt
+History.txt
+Logging.txt
+Manifest.txt
+PostInstall.txt
+README.rdoc
+Rakefile
+RuoteParticipants.txt
+TODO.txt
+app_generators/daemon_kit/USAGE
+app_generators/daemon_kit/daemon_kit_generator.rb
+app_generators/daemon_kit/templates/README
+app_generators/daemon_kit/templates/Rakefile
+app_generators/daemon_kit/templates/bin/daemon.erb
+app_generators/daemon_kit/templates/config/arguments.rb
+app_generators/daemon_kit/templates/config/boot.rb
+app_generators/daemon_kit/templates/config/environment.rb
+app_generators/daemon_kit/templates/config/environments/development.rb
+app_generators/daemon_kit/templates/config/environments/production.rb
+app_generators/daemon_kit/templates/config/environments/test.rb
+app_generators/daemon_kit/templates/config/post-daemonize/readme
+app_generators/daemon_kit/templates/config/pre-daemonize/readme
+app_generators/daemon_kit/templates/lib/daemon.rb
+app_generators/daemon_kit/templates/libexec/daemon.erb
+app_generators/daemon_kit/templates/script/console
+app_generators/daemon_kit/templates/script/destroy
+app_generators/daemon_kit/templates/script/generate
+bin/daemon_kit
+daemon_generators/amqp/USAGE
+daemon_generators/amqp/amqp_generator.rb
+daemon_generators/amqp/templates/config/amqp.yml
+daemon_generators/amqp/templates/config/initializers/amqp.rb
+daemon_generators/amqp/templates/libexec/daemon.rb
+daemon_generators/cron/USAGE
+daemon_generators/cron/cron_generator.rb
+daemon_generators/cron/templates/config/initializers/cron.rb
+daemon_generators/cron/templates/libexec/daemon.rb
+daemon_generators/cucumber/USAGE
+daemon_generators/cucumber/cucumber_generator.rb
+daemon_generators/cucumber/templates/cucumber
+daemon_generators/cucumber/templates/cucumber.rake
+daemon_generators/cucumber/templates/cucumber_environment.rb
+daemon_generators/cucumber/templates/env.rb
+daemon_generators/deploy_capistrano/deploy_capistrano_generator.rb
+daemon_generators/deploy_capistrano/templates/Capfile
+daemon_generators/deploy_capistrano/templates/USAGE
+daemon_generators/deploy_capistrano/templates/config/deploy.rb
+daemon_generators/deploy_capistrano/templates/config/deploy/production.rb
+daemon_generators/deploy_capistrano/templates/config/deploy/staging.rb
+daemon_generators/deploy_capistrano/templates/config/environments/staging.rb
+daemon_generators/jabber/USAGE
+daemon_generators/jabber/jabber_generator.rb
+daemon_generators/jabber/templates/config/initializers/jabber.rb
+daemon_generators/jabber/templates/config/jabber.yml
+daemon_generators/jabber/templates/libexec/daemon.rb
+daemon_generators/nanite_agent/USAGE
+daemon_generators/nanite_agent/nanite_agent_generator.rb
+daemon_generators/nanite_agent/templates/config/initializers/nanite_agent.rb
+daemon_generators/nanite_agent/templates/config/nanite.yml
+daemon_generators/nanite_agent/templates/lib/actors/sample.rb
+daemon_generators/nanite_agent/templates/libexec/daemon.rb
+daemon_generators/rspec/USAGE
+daemon_generators/rspec/rspec_generator.rb
+daemon_generators/rspec/templates/spec.rb
+daemon_generators/rspec/templates/spec/spec.opts
+daemon_generators/rspec/templates/spec/spec_helper.rb
+daemon_generators/rspec/templates/tasks/rspec.rake
+daemon_generators/ruote/USAGE
+daemon_generators/ruote/ruote_generator.rb
+daemon_generators/ruote/templates/config/amqp.yml
+daemon_generators/ruote/templates/config/initializers/ruote.rb
+daemon_generators/ruote/templates/config/ruote.yml
+daemon_generators/ruote/templates/lib/daemon.rb
+daemon_generators/ruote/templates/lib/sample.rb
+daemon_generators/ruote/templates/libexec/daemon.rb
+lib/daemon_kit.rb
+lib/daemon_kit/abstract_logger.rb
+lib/daemon_kit/amqp.rb
+lib/daemon_kit/application.rb
+lib/daemon_kit/arguments.rb
+lib/daemon_kit/commands/console.rb
+lib/daemon_kit/config.rb
+lib/daemon_kit/console_daemon.rb
+lib/daemon_kit/core_ext.rb
+lib/daemon_kit/core_ext/configurable.rb
+lib/daemon_kit/core_ext/string.rb
+lib/daemon_kit/cron.rb
+lib/daemon_kit/cucumber/world.rb
+lib/daemon_kit/deployment/capistrano.rb
+lib/daemon_kit/em.rb
+lib/daemon_kit/error_handlers/base.rb
+lib/daemon_kit/error_handlers/hoptoad.rb
+lib/daemon_kit/error_handlers/mail.rb
+lib/daemon_kit/exceptions.rb
+lib/daemon_kit/initializer.rb
+lib/daemon_kit/jabber.rb
+lib/daemon_kit/nanite.rb
+lib/daemon_kit/nanite/agent.rb
+lib/daemon_kit/pid_file.rb
+lib/daemon_kit/ruote_participants.rb
+lib/daemon_kit/ruote_pseudo_participant.rb
+lib/daemon_kit/ruote_workitem.rb
+lib/daemon_kit/safety.rb
+lib/daemon_kit/tasks.rb
+lib/daemon_kit/tasks/environment.rake
+lib/daemon_kit/tasks/framework.rake
+lib/daemon_kit/tasks/god.rake
+lib/daemon_kit/tasks/log.rake
+lib/daemon_kit/tasks/monit.rake
+script/console
+script/destroy
+script/generate
+script/txt2html
+spec/abstract_logger_spec.rb
+spec/argument_spec.rb
+spec/config_spec.rb
+spec/configurable_spec.rb
+spec/daemon_kit_spec.rb
+spec/error_handlers_spec.rb
+spec/fixtures/env.yml
+spec/fixtures/noenv.yml
+spec/initializer_spec.rb
+spec/spec.opts
+spec/spec_helper.rb
+tasks/rspec.rake
+templates/god/god.erb
+templates/monit/monit.erb
+test/test_amqp_generator.rb
+test/test_cron_generator.rb
+test/test_daemon-kit_generator.rb
+test/test_daemon_kit_config.rb
+test/test_deploy_capistrano_generator.rb
+test/test_generator_helper.rb
+test/test_helper.rb
+test/test_jabber_generator.rb
+test/test_nanite_agent_generator.rb
+test/test_ruote_generator.rb
+vendor/tmail-1.2.3/tmail.rb
+vendor/tmail-1.2.3/tmail/address.rb
+vendor/tmail-1.2.3/tmail/attachments.rb
+vendor/tmail-1.2.3/tmail/base64.rb
+vendor/tmail-1.2.3/tmail/compat.rb
+vendor/tmail-1.2.3/tmail/config.rb
+vendor/tmail-1.2.3/tmail/core_extensions.rb
+vendor/tmail-1.2.3/tmail/encode.rb
+vendor/tmail-1.2.3/tmail/header.rb
+vendor/tmail-1.2.3/tmail/index.rb
+vendor/tmail-1.2.3/tmail/interface.rb
+vendor/tmail-1.2.3/tmail/loader.rb
+vendor/tmail-1.2.3/tmail/mail.rb
+vendor/tmail-1.2.3/tmail/mailbox.rb
+vendor/tmail-1.2.3/tmail/main.rb
+vendor/tmail-1.2.3/tmail/mbox.rb
+vendor/tmail-1.2.3/tmail/net.rb
+vendor/tmail-1.2.3/tmail/obsolete.rb
+vendor/tmail-1.2.3/tmail/parser.rb
+vendor/tmail-1.2.3/tmail/port.rb
+vendor/tmail-1.2.3/tmail/quoting.rb
+vendor/tmail-1.2.3/tmail/require_arch.rb
+vendor/tmail-1.2.3/tmail/scanner.rb
+vendor/tmail-1.2.3/tmail/scanner_r.rb
+vendor/tmail-1.2.3/tmail/stringio.rb
+vendor/tmail-1.2.3/tmail/utils.rb
+vendor/tmail-1.2.3/tmail/version.rb
+vendor/tmail.rb

data/vendor/daemon-kit/PostInstall.txt

@@ -0,0 +1,6 @@
+
+For more information on daemon-kit, see http://kit.rubyforge.org/daemon-kit
+
+To get started quickly run 'daemon_kit' without any arguments
+
+

data/vendor/daemon-kit/README.rdoc

@@ -0,0 +1,130 @@
+= Daemon Kit
+
+* http://kit.rubyforge.org/daemon-kit/rdoc/
+* http://kit.rubyforge.org/daemon-kit (coming soon)
+* http://groups.google.com/group/daemon-kit (daemon-kit@googlegroups.com)
+* #daemon-kit on Freenode
+
+== Description
+
+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 created evented and non-evented daemons that perform a multitude of different tasks.
+
+Supported generators:
+
+* XMPP bot (non-evented)
+* AMQP consumer (evented)
+* Nanite agent
+* Cron-style daemon
+* ruote remote participants
+
+== Features/Problems
+
+* Build it
+* Review TODO.txt
+
+== Synopsis
+
+  $ 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 jabber
+
+Use the 'jabber' generator instead of the default one.
+
+== Generators
+
+Currently six generators exist: default, jabber, amqp, cron, nanite & ruote
+
+The default generator creates a simple daemon with an infinite loop inside that you can adapt.
+
+=== Jabber Generator
+
+The jabber generator creates a simple daemon that leverages the "xmpp4r-simple":http://xmpp4r-simple.rubyforge.org/ 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.
+
+=== Cron Generator
+
+The cron generator creates a simple daemon that leverages the "rufus-scheduler":http://github.com/jmettraux/rufus-scheduler gem to create a simple cron-lie daemon. Please be aware that this daemon could never be a replacement for the battle-tested "cron utility":http://www.gentoo.org/doc/en/cron-guide.xml shipped standard with most *nix distributions.
+
+=== AMQP Consumer Generator
+
+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":http://github.com/tmm1/amqp gem.
+
+=== Nanite Agent Generator
+
+The "nanite":http://github.com/ezmobius/nanite agent generator gets you up and running with nanite agents very quickly.
+
+=== ruote Remote Participants
+
+The "ruote":http://openwfe.rubyforge.org 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.
+
+== Requirements
+
+* Ruby 1.8.6
+* eventmachine-0.12.8[http://rubyeventmachine.com]
+* rspec (for writing/running your specs)
+
+== Generator Requirements
+
+Depending on the generator you choose for your daemon, it might require additional gems to run.
+
+* jabber - xmpp4r-simple[http://xmpp4r-simple.rubyforge.org]
+* cron - rufus-scheduler[http://github.com/jmettraux/rufus-scheduler] (at least version 2.0.0)
+* amqp - amqp[http://github.com/tmm1/amqp]
+* nanite - nanite[http://github.com/ezmobius/nanite]
+* ruote - none, although ruote[http://openwfe.rubyforge.org] should probably be running somewhere
+
+== Install
+
+Currently recommended to stick to the git repo:
+
+  $ git clone git://github.com/kennethkalmer/daemon-kit.git
+  $ rake gem
+  $ gem install pkg/daemon-kit-X.X.X.gem
+
+Development versions are available as gems from github:
+
+  $ gem install kennethkalmer-daemon-kit -s http://gems.github.com
+
+Stable versions, when released are available directly from Rubyforge:
+
+  $ gem install daemon-kit
+
+== Further reading
+
+* Configuration.txt
+* Deployment.txt
+* Logging.txt
+* RuoteParticipants.txt
+* http://www.opensourcery.co.za/tag/daemon-kit/
+
+== License
+
+(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.

data/vendor/daemon-kit/Rakefile

@@ -0,0 +1,37 @@
+require 'rubygems'
+gem 'hoe', '>= 2.1.0'
+require 'hoe'
+require 'fileutils'
+require File.dirname(__FILE__) + '/lib/daemon_kit'
+
+Hoe.plugin :newgem
+Hoe.plugin :website
+# Hoe.plugin :cucumberfeatures
+
+# Generate all the Rake tasks
+# Run 'rake -T' to see list of generated tasks (from gem root directory)
+$hoe = Hoe.spec('daemon-kit') do |p|
+  p.summary = '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.'
+  p.developer('Kenneth Kalmer', 'kenneth.kalmer@gmail.com')
+  p.changes              = p.paragraphs_of("History.txt", 0..1).join("\n\n")
+  p.post_install_message = IO.read( 'PostInstall.txt' ) # TODO remove if post-install message not required
+  p.rubyforge_name       = 'kit' # TODO this is default value
+  p.extra_deps = [
+                  ['rubigen', '>= 1.5.2'],
+                  ['eventmachine', '>=0.12.8']
+                 ]
+  p.extra_dev_deps = [
+                      ['newgem', ">= #{::Newgem::VERSION}"]
+                     ]
+
+  p.clean_globs |= %w[**/.DS_Store tmp *.log]
+  path = (p.rubyforge_name == p.name) ? p.rubyforge_name : "\#{p.rubyforge_name}/\#{p.name}"
+  p.remote_rdoc_dir = File.join(path.gsub(/^#{p.rubyforge_name}\/?/,''), 'rdoc')
+  p.rsync_args = '-av --delete --ignore-errors'
+end
+
+require 'newgem/tasks' # load /tasks/*.rake
+Dir['tasks/**/*.rake'].each { |t| load t }
+
+# TODO - want other tests/tasks run by default? Add them to the list
+task :default => [:spec] #, :features]

data/vendor/daemon-kit/RuoteParticipants.txt

@@ -0,0 +1,113 @@
+= Writing remote ruote participants with daemon-kit
+
+daemon-kit is an ideal housing for remote ruote participants, providing a lot
+of convenience in terms of receiving and sending workitems, delegating work to
+pseudo-participant classes, handling configuration of the communication channel
+between ruote and the remote participant, and much more.
+
+== What is ruote?
+
+Ruote is a Ruby workflow engine. It is a powerful tool for defining, running and
+orchestrating business processes.
+
+* http://openwferu.rubyforge.org/
+* http://www.opensourcery.co.za/2009/03/04/ruote-in-20-minutes/
+* http://www.opensourcery.co.za/2009/07/06/driving-business-processes-in-ruby/
+
+== What are remote participants?
+
+Remote participants are participants that perform their work in a different
+Ruby processes from the one running the engine. This is useful in two cases,
+possibily many more, that involves autonomous participants.
+
+* Autonomous participants located on remote servers, driven by identity
+* Clustering autonomous participants to process workitems from a queue
+
+To learn more about the differences between local and remote participants
+please see http://openwferu.rubyforge.org/part.html
+
+Currently on the AMQP components are in place in daemon-kit, with XMPP coming
+soon.
+
+== Creating a remote participant with daemon-kit
+
+Generate your daemon using the 'ruote' generator:
+
+  $ daemon_kit partd -i ruote
+
+Make sure you have the JSON gem install, and the AMQP gem as well.
+
+== Configuring the daemon
+
+You need to review +config/ruote.yml+ to specify the AMQP queues that the daemon
+will subscribe to for receiving workitems. You'll also need to configure the 
+AMQP gem be updating +config/amqp.yml+
+
+The generated daemon in +libexec/+ already defaults to using AMQP as a transport
+for workitems.
+
+== Writing pseudo-participants
+
+Pseudo-participants in daemon-kit are pure Ruby classes. Implement your classes
+in +lib/+ and require them from +lib/<daemon_name>.rb+.
+
+Register your classes as pseudo-participants by registering them in the daemon
+file in +libexec+, just as the Sample class is registered in the generated
+code. Your class will be instantiated upon registration, and will be re-used
+for every incoming workitem passed to it.
+
+All your public methods in the pseudo-participant classes should be accept
+a single parameter, which is a ruote workitem in pure Hash form.
+
+== Wiring up the remote participant in ruote
+
+See the complete code here: http://gist.github.com/144861
+
+A sample process definition might look something like this:
+
+  class QuoteProcess < OpenWFE::ProcessDefinition
+    sequence do
+      kit :command => '/sample/quote', :queue => 'work1'
+
+      console
+    end
+  end
+
++kit+ in the above process definition is registered with the ruote engine as an
+AMQPParticipant. The AMQPParticipant delivers workitems to the specified AMQP
+queue.
+
+Based on the values in +config/ruote.yml+, your daemon will be subscribed to
+those queues.
+
+The second part is delegating the workitem inside the daemon to the correct
+pseudo-participant. This is handled by the +:command+ parameter in the process
+definition. DaemonKit::Workitem looks at the command parameter of the incoming
+workitem, and then finds a registered pseudo-participant instance and calls the
+requested method on that class.
+
+The +:command+ parameter follows the following convention (stolen shamelessly
+from Nanite):
+
+  :command => '/class_name/method_name'
+
+When classes are registered, the name of the class is downcased and camel-case
+words are separated by underscores. Method names are not changed, but methods
+are required to be public.
+
+== Processing workitems and replying to the engine
+
+The methods called in the pseudo-participants receive a single parameter, a
+ruote workitem as a hash. The participant is then free to analyze the hash
+and perform the appropriate actions required. The return value of the method
+is discarded, and the workitem is returned back to the engine. If the method
+modified the workitem, these changes will be sent along as well.
+
+== Random other notes
+
+Apart from configuring the AMPQ client (or XMPP in future) and the ruote.yml
+file, daemon developers don't need to worry about anything related to receiving
+workitems or sending replies.
+
+Our aim is to allow you to swap between participants on both sides of the
+transport without changing any of your code.