daemon-kit 0.2.3 → 0.3.0.rc1

checksums.yaml

@@ -1,15 +1,7 @@
 ---
-!binary "U0hBMQ==":
-  metadata.gz: !binary |-
-    ZWU3ZTg1MjM1MzNiY2QxMThkODg2OWE0NDk1ZjBmZWZhZWM2MDkyZA==
-  data.tar.gz: !binary |-
-    OTBhNWQwMWZkZDRiMGE5YjE4YWUxYjRlNDg1YjYxYzVmNzdkMmFmZQ==
-!binary "U0hBNTEy":
-  metadata.gz: !binary |-
-    YTkzN2E2MjJiYmYzZTFmZWQ4YWRkZTFjMTk3OGY3NDY1OGJjOGVlODgwNDZj
-    OTNkMzBiYTIwYzg4MzQ1YzE3M2EzMmMxNmY0MmM5NzA4MjJhMmM1M2FlNDcy
-    NzM3N2ZmNGY0MGJlYzYzMjAzMjYxNjhlMWUxZDRmM2E4YTM2ZDk=
-  data.tar.gz: !binary |-
-    M2ZiZWQzYjU5ZmQ1Y2YxMjdkNDFmYWVjNzQ5ZDkzNTY1M2U5ZDNiYWNhYjRl
-    YzI1YmY1MjBhYTQyMGJiMGY1ZGU2MzMwNmNmMTkzYTJiMDhiYmVkZTc2YjAw
-    MDYwNDUxY2E0Nzc5N2ZkYTk1ZjRjMGUxYTBjZmRmZGVhNDkxNDE=
+SHA1:
+  metadata.gz: 9356410391db8c1c25d11bed90a08e76fba383a3
+  data.tar.gz: c87d71466d79190914007f2596262df9c8b338fd
+SHA512:
+  metadata.gz: 4d58c735226158c03e18e936f1fdb39d8387bf59f464265c0694312825e23b6d0d9ba850fa13102fdb4ebfcc860fec035b338bf3579cb9b79209d41db0221138
+  data.tar.gz: e601935b3e7798ca8dd232ffa31ec15c3aab44aa14024fcca41f6b03f099f2936e898f9858154718bb9cb844aad1d646b514ff568caa4794b97ed97d3715b77e

data/.travis.yml

@@ -0,0 +1,15 @@
+language: ruby
+rvm:
+  - 2.0.0
+  - 1.9.3
+  - 1.9.2
+  - rbx-19mode
+  - 1.8.7
+  - ree
+matrix:
+  allow_failures:
+    - rvm: jruby-19mode
+    - rvm: rbx-19mode
+    - rvm: 1.8.7
+    - rvm: ree
+before_install: umask 0022

data/Gemfile

@@ -1,4 +1,4 @@
-source 'http://rubygems.org'
+source 'https://rubygems.org'
 
 # Specify your gem's dependencies in daemon-kit.gemspec
 gemspec

data/History.txt

@@ -1,3 +1,7 @@
+== 0.3.0 (In progress)
+
+* Removed nanite support, nanite hasn't released in years.
+
 == 0.2.0 2012-09-30
 
 * Depend on the 'safely' gem for the safely method and logging backtraces

data/{README.rdoc → README.md}

@@ -1,11 +1,15 @@
-= Daemon Kit
+# Daemon Kit
+
+[![Code Climate](https://codeclimate.com/github/kennethkalmer/daemon-kit.png)](https://codeclimate.com/github/kennethkalmer/daemon-kit)
+[![Gem Version](https://badge.fury.io/rb/daemon-kit.png)](http://badge.fury.io/rb/daemon-kit)
+[![Build Status](https://travis-ci.org/kennethkalmer/daemon-kit.png)](https://travis-ci.org/kennethkalmer/daemon-kit)
 
 * https://github.com/kennethkalmer/daemon-kit/wiki
 * http://rdoc.info/github/kennethkalmer/daemon-kit
 * http://groups.google.com/group/daemon-kit (daemon-kit@googlegroups.com)
-* #daemon-kit on Freenode
+* \#daemon-kit on Freenode
 
-== Description
+## 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.
 
@@ -16,90 +20,95 @@ Supported generators:
 * XMPP bot (evented)
 * AMQP consumer (evented)
 * SQS consumer
-* Nanite agent
+* Nanite agent (requires < 0.3)
 * Cron-style daemon
 * ruote remote participants
 
-== Features/Problems
+## Features/Problems
 
 * Build it
 * Review TODO.txt
 
-== Synopsis
+## 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 xmpp
+```
 
 Use the 'xmpp' generator instead of the default one.
 
-== Generators
+## Generators
 
-Currently six generators exist: default, xmpp, amqp, cron, nanite & ruote
+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.
 
-=== XMPP Generator
-
-The jabber generator creates a simple daemon that leverages the blather[http://blather.squishtech.com/] 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
+### XMPP 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[http://www.gentoo.org/doc/en/cron-guide.xml] utility shipped standard with most *nix distributions.
+The jabber generator creates a simple daemon that leverages the [blather](http://blather.squishtech.com/) 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.
 
-=== AMQP Consumer Generator
+### Cron 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/ruby-amqp/amqp] gem.
+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[http://www.gentoo.org/doc/en/cron-guide.xml] utility shipped standard with most *nix distributions.
 
-=== Nanite Agent Generator
+### AMQP Consumer Generator
 
-The nanite[http://github.com/ezmobius/nanite] agent generator gets you up and running with nanite agents very quickly.
+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/ruby-amqp/amqp) gem.
 
-=== ruote Remote Participants
+### 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.
+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
+## Requirements
 
 * Ruby 1.8.7 or later (developed on REE/1.9.1)
-* eventmachine-0.12.10[http://rubyeventmachine.com]
+* [eventmachine-0.12.10](http://rubyeventmachine.com)
 * rspec (for writing/running your specs)
 
-== Generator Requirements
+## Generator Requirements
 
 Depending on the generator you choose for your daemon, it might require additional gems to run.
 
-* xmpp - blather[http://blather.squishtech.com/]
-* 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
+* xmpp - [blather](http://blather.squishtech.com/)
+* cron - [rufus-scheduler](http://github.com/jmettraux/rufus-scheduler) (at least version 2.0.0)
+* amqp - [amqp](http://github.com/tmm1/amqp)
+* ruote - none, although [ruote](http://openwfe.rubyforge.org) should probably be running somewhere
 
-The generators are all written using Thor[http://rdoc.info/rdoc/wycats/thor], which is bundled with daemon-kit and not needed for running any of the generators.
+The generators are all written using [Thor](http://rdoc.info/rdoc/wycats/thor), which is bundled with daemon-kit and not needed for running any of the generators.
 
-== Install
+## Install
 
 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 Gemcutter:
+Stable versions, when released are available directly from Rubygems:
 
+```
   $ gem install daemon-kit
+```
 
-== Upgrading
+## Upgrading
 
 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.
 
-== Further reading
+## Further reading
 
 * Configuration.txt
 * Deployment.txt
@@ -107,7 +116,7 @@ When upgrading daemons generated from earlier versions of daemon-kit, it is easi
 * RuoteParticipants.txt
 * http://www.opensourcery.co.za/tag/daemon-kit/
 
-== License
+## License
 
 (The MIT License)
 

data/Rakefile

@@ -4,4 +4,4 @@ require "bundler/gem_tasks"
 Dir['tasks/**/*.rake'].each { |t| load t }
 
 # TODO - want other tests/tasks run by default? Add them to the list
-task :default => [:spec] #, :features]
+task :default => [:spec, :features]

data/bin/daemon-kit

@@ -12,6 +12,10 @@ if %w(-v --version).include? ARGV.first
   exit(0)
 end
 
+if ARGV.empty?
+  ARGV.push '--help'
+end
+
 require 'daemon_kit/generators'
 require 'generators/daemon_kit/app/app_generator'
 

data/daemon-kit.gemspec

@@ -30,21 +30,21 @@ $ daemon-kit -h
                           "Deployment.txt",
                           "History.txt",
                           "Logging.txt",
-                          "README.rdoc",
+                          "README.md",
                           "RuoteParticipants.txt",
                           "TODO.txt",
                          ]
 
-  gem.add_dependency(%q<thor>)
   gem.add_development_dependency(%q<bundler>)
-  gem.add_development_dependency(%q<rake>)  
+  gem.add_development_dependency(%q<rake>)
   gem.add_development_dependency(%q<rdoc>)
   gem.add_development_dependency(%q<rspec>, ["~> 2.6"])
-  gem.add_development_dependency(%q<cucumber>, ["~> 0.10.0"])
-  gem.add_development_dependency(%q<mocha>, ["~> 0.9.12"])
+  gem.add_development_dependency(%q<cucumber>, ["~> 1.3.8"])
+  gem.add_development_dependency(%q<aruba>, ["~> 0.5.3"])
   gem.add_development_dependency(%q<SyslogLogger>)
+
+  gem.add_dependency(%q<thor>)
   gem.add_runtime_dependency(%q<eventmachine>, [">= 0.12.10"])
   gem.add_runtime_dependency(%q<safely>, [">= 0.3.1"])
-  gem.add_runtime_dependency(%q<rubigen>)
   gem.add_runtime_dependency(%q<i18n>)
 end

data/features/amqp_generator.feature

@@ -0,0 +1,27 @@
+Feature: AMQP generator provides some additional infrastructure
+
+  Scenario: Using AMQP generator when generating a new daemon
+    When I run `daemon-kit vuvuzela -i amqp`
+    And I cd to "vuvuzela"
+    Then the following files should exist:
+      | config/amqp.yml |
+      | config/pre-daemonize/amqp.rb |
+      | libexec/vuvuzela-daemon.rb |
+    And the file "Gemfile" should contain:
+    """
+    gem 'amqp'
+    """
+
+  Scenario: Using AMQP generator on an existing daemon
+    Given I have an existing daemon called "vuvuzela"
+    And I cd to "vuvuzela"
+    When I run `./script/generate amqp` interactively
+    And I accept the conflicts
+    Then the following files should exist:
+      | config/amqp.yml |
+      | config/pre-daemonize/amqp.rb |
+      | libexec/vuvuzela-daemon.rb |
+    And the file "Gemfile" should contain:
+    """
+    gem 'amqp'
+    """

data/features/app_generator.feature

@@ -0,0 +1,46 @@
+Feature: Generating a new daemon
+
+  daemon-kit offers an application generator to get you started.
+
+  Scenario: Generator offers help when no arguments are provided
+    When I run `daemon-kit`
+    Then the output should contain:
+    """
+    Usage:
+      daemon-kit app APP_PATH
+      """
+
+  Scenario: Generator offers help when asked
+    When I run `daemon-kit --help`
+    Then the output should contain:
+    """
+    Usage:
+      daemon-kit app APP_PATH
+    """
+
+  Scenario: Generating a default daemon
+    When I run `daemon-kit vuvuzela`
+    And I cd to "vuvuzela"
+    Then the following files should exist:
+      | Gemfile |
+      | README |
+      | Rakefile |
+      | bin/vuvuzela |
+      | config/arguments.rb |
+      | config/boot.rb |
+      | config/environments/development.rb |
+      | config/environments/test.rb |
+      | config/environments/production.rb |
+      | config/pre-daemonize/readme |
+      | config/post-daemonize/readme |
+      | lib/vuvuzela.rb |
+      | libexec/vuvuzela-daemon.rb |
+      | script/console |
+      | script/destroy |
+      | script/generate |
+      | spec/spec_helper.rb |
+    And the following directories should exist:
+      | log |
+      | tasks |
+      | vendor |
+      | tmp |

data/features/capistrano_generator.feature

@@ -0,0 +1,30 @@
+Feature: Capistrano generator provides some additional infrastructure
+
+  Scenario: Using the capistrano generator when generating a new daemon
+    When I run `daemon-kit vuvuzela -d capistrano`
+    And I cd to "vuvuzela"
+    Then the following files should exist:
+      | Capfile |
+      | config/deploy.rb |
+      | config/deploy/staging.rb |
+      | config/deploy/production.rb |
+    And the file "Gemfile" should contain:
+    """
+    gem 'capistrano'
+    gem 'capistrano-ext'
+    """
+
+  Scenario: Using AMQP generator on an existing daemon
+    Given I have an existing daemon called "vuvuzela"
+    And I cd to "vuvuzela"
+    When I run `./script/generate capistrano`
+    Then the following files should exist:
+      | Capfile |
+      | config/deploy.rb |
+      | config/deploy/staging.rb |
+      | config/deploy/production.rb |
+    And the file "Gemfile" should contain:
+    """
+    gem 'capistrano'
+    gem 'capistrano-ext'
+    """

data/features/cron_generator.feature

@@ -0,0 +1,26 @@
+Feature: Cron generator
+
+  Scenario: Using cron generator when generating a new daemon
+    When I run `daemon-kit vuvuzela -i cron`
+    And I cd to "vuvuzela"
+    Then the following files should exist:
+      | config/pre-daemonize/cron.rb |
+      | libexec/vuvuzela-daemon.rb |
+    And the file "Gemfile" should contain:
+    """
+    gem 'rufus-scheduler'
+    """
+
+  Scenario: Using AMQP generator on an existing daemon
+    Given I have an existing daemon called "vuvuzela"
+    And I cd to "vuvuzela"
+    When I run `./script/generate cron` interactively
+    And I accept the conflicts
+    Then the following files should exist:
+      | config/pre-daemonize/cron.rb |
+      | libexec/vuvuzela-daemon.rb |
+    And the file "Gemfile" should contain:
+    """
+    gem 'rufus-scheduler'
+    """
+

data/features/ruote_generator.feature

@@ -0,0 +1,27 @@
+Feature: Ruote remote participant generator
+
+  Scenario: Using ruote generator when generating a new daemon
+    When I run `daemon-kit vuvuzela -i ruote`
+    And I cd to "vuvuzela"
+    Then the following files should exist:
+      | config/amqp.yml |
+      | config/pre-daemonize/ruote.rb |
+      | lib/vuvuzela.rb |
+      | lib/sample.rb |
+      | libexec/vuvuzela-daemon.rb |
+    And the file "Gemfile" should contain "gem 'amqp'"
+    And the file "Gemfile" should contain "gem 'json'"
+
+  Scenario: Using AMQP generator on an existing daemon
+    Given I have an existing daemon called "vuvuzela"
+    And I cd to "vuvuzela"
+    When I run `./script/generate ruote` interactively
+    And I accept the conflicts
+    Then the following files should exist:
+      | config/amqp.yml |
+      | config/pre-daemonize/ruote.rb |
+      | lib/vuvuzela.rb |
+      | lib/sample.rb |
+      | libexec/vuvuzela-daemon.rb |
+    And the file "Gemfile" should contain "gem 'amqp'"
+    And the file "Gemfile" should contain "gem 'json'"

data/features/sqs_generator.feature

@@ -0,0 +1,21 @@
+Feature: SQS generator
+
+  Scenario: Using SQS generator when generating a new daemon
+    When I run `daemon-kit vuvuzela -i sqs`
+    And I cd to "vuvuzela"
+    Then the following files should exist:
+      | config/sqs.yml |
+      | config/pre-daemonize/sqs.rb |
+      | libexec/vuvuzela-daemon.rb |
+    And the file "Gemfile" should contain "gem 'aws-sdk'"
+
+  Scenario: Using AMQP generator on an existing daemon
+    Given I have an existing daemon called "vuvuzela"
+    And I cd to "vuvuzela"
+    When I run `./script/generate sqs` interactively
+    And I accept the conflicts
+    Then the following files should exist:
+      | config/sqs.yml |
+      | config/pre-daemonize/sqs.rb |
+      | libexec/vuvuzela-daemon.rb |
+    And the file "Gemfile" should contain "gem 'aws-sdk'"

data/features/step_definitions/daemon_steps.rb

@@ -0,0 +1,10 @@
+Given(/^I have an existing daemon called "(.*?)"$/) do |name|
+  step %Q{I run `daemon-kit #{name}`}
+end
+
+
+When(/^I accept the conflicts$/) do
+  step %Q{I wait for stdout to contain "Overwrite"}
+  type "a\n"
+  #eot
+end