apphunkd 0.9.0

data/spec/lib/apphunkd/remote_spec.rb

@@ -0,0 +1,61 @@
+require File.dirname(__FILE__) + '/../../spec_helper'
+
+describe Apphunkd::Remote do
+  before(:each) do
+    @remote = Apphunkd::Remote
+    @mock_uri = mock('URI', :path => '/home', :user => nil, :host => 'localhost', :port => 80)
+    URI.stub!(:parse).and_return(@mock_uri)
+    Net::HTTP.stub!(:post_form)
+  end
+  
+  it 'should parse the url' do
+    URI.should_receive(:parse).with('http://example.org').and_return(@mock_uri)
+    @remote.post('http://example.org')
+  end
+  
+  it 'should send the payload to a specified parsed uri' do
+    Net::HTTP.should_receive(:post_form).with(@mock_uri, { :value => 'home' })
+    @remote.post('http://example.org', { :value => 'home' })
+  end
+  
+  context 'timeout' do
+    it 'should wrap the post in a default Timeout of 30 seconds' do
+      Timeout.should_receive(:timeout).with(30)
+      @remote.post('http://example.org', { :value => 'home' })
+    end
+    
+    it 'should accept a timeout as additional argument' do
+      Timeout.should_receive(:timeout).with(50)
+      @remote.post('http://example.org', { :value => 'home' }, 50)
+    end
+  end
+  
+  context 'result' do
+    before(:each) do
+      @mock_net_response = mock('Net::HTTPResponse', :code => 200)
+      Net::HTTP.stub!(:post_form).and_return(@mock_net_response)
+    end
+    
+    it 'should return status :timeout if the time run out' do
+      Timeout.should_receive(:timeout).and_raise(Timeout::Error)
+      result = @remote.post('http://example.org', { :value => 'home' }, 0)
+      result.status.should == :timeout
+    end
+
+    it 'should return status :connection_error if the connection failed' do
+      Net::HTTP.should_receive(:post_form).and_raise(SocketError)
+      result = @remote.post('http://example.org', { :value => 'home' }, 0)
+      result.status.should == :connection_error
+    end
+    
+    it 'should return the status code' do
+      result = @remote.post('http://example.org', { :value => 'home' }, 0)
+      result.status.should == :ok
+    end
+    
+    it 'should return the original response' do
+      result = @remote.post('http://example.org', { :value => 'home' }, 0)
+      result.response == @mock_net_response
+    end
+  end
+end

data/spec/lib/apphunkd_spec.rb

@@ -0,0 +1,50 @@
+require File.dirname(__FILE__) + '/../spec_helper.rb'
+
+describe Apphunkd do
+  describe "#run!" do
+    before(:each) do
+      Apphunkd.stub!(:initialize_queue)
+      Apphunkd.stub!(:initialize_api_service)
+    end
+
+    it "should initialize the queue" do
+      Apphunkd.should_receive(:initialize_queue)
+      Apphunkd.run!
+    end
+
+    it "should initialize the api service" do
+      Apphunkd.should_receive(:initialize_api_service)
+      Apphunkd.run!
+    end
+  end
+
+  describe "#initialize_queue" do
+    before(:each) do
+      @queue = mock('Queue instance')
+      Apphunkd::Queue.stub!(:new).and_return(@queue)
+    end
+
+    it "should create and assign a new Queue instance" do
+      @queue.stub!(:activate!)
+      Apphunkd.initialize_queue
+      Apphunkd.queue.should eql(@queue)
+    end
+
+    it 'activate the queue' do
+      @queue.should_receive(:activate!)
+      Apphunkd.initialize_queue
+    end
+  end
+
+  describe '#initialize_api_service' do
+    it 'should start the api service' do
+      Apphunkd::API::Service.should_receive(:run!)
+      Apphunkd.initialize_api_service
+    end
+
+    it 'should start on 127.0.0.1:8212' do
+      Apphunkd::API::Service.should_receive(:run!).with(:port => '8212', :host => '127.0.0.1')
+      Apphunkd.initialize_api_service
+    end
+  end
+end

data/spec/spec.opts

@@ -0,0 +1 @@
+--colour

data/spec/spec_helper.rb

@@ -0,0 +1,13 @@
+begin
+  require 'spec'
+rescue LoadError
+  require 'rubygems'
+  gem 'rspec'
+  require 'spec'
+end
+
+require File.dirname(__FILE__) + '/../config/environment'
+DaemonKit::Application.running!
+
+Spec::Runner.configure do |config|
+end

data/support/apphunkd.initd

@@ -0,0 +1,47 @@
+#!/usr/bin/env ruby
+#
+# apphunkd       Startup script for apphunkd by Andreas Wolff
+#
+# description: apphunkd is a daemon for sending messages from your applications to apphunk.com
+#
+
+def start
+  puts "Starting.."
+  `apphunkd start -e production`
+end
+
+def stop
+  puts "Stopping.."
+  `apphunkd stop -e production`
+end
+
+def restart
+  stop
+  start
+end
+
+def status
+  if File.exist?('/var/run/apphunkd.pid')
+    pid = File.readlines('/var/run/apphunkd.pid')[0].chomp
+    puts "apphunkd running (#{pid}).."
+  else
+    puts "apphunkd not running.."
+  end
+end
+
+
+unless ['start', 'stop', 'restart', 'status'].include? ARGV.first
+    puts "Usage: apphunkd {start|stop|restart|status}"
+    exit
+end
+
+case
+when ARGV.include?('start')
+  start
+when ARGV.include?('stop')
+  stop
+when ARGV.include?('restart')
+  restart
+when ARGV.include?('status')
+  status
+end

data/support/apphunkd.monitrc

@@ -0,0 +1,3 @@
+check process apphunkd with pidfile /var/run/apphunkd.pid
+  start program = "/etc/init.d/apphunkd start"
+  stop program = "/etc/init.d/apphunkd stop"  

data/tasks/rspec.rake

@@ -0,0 +1,21 @@
+# begin
+#   require 'spec'
+# rescue LoadError
+#   require 'rubygems'
+#   require 'spec'
+# end
+# begin
+#   require 'spec/rake/spectask'
+# rescue LoadError
+#   puts <<-EOS
+# To use rspec for testing you must install rspec gem:
+#     gem install rspec
+# EOS
+#   exit(0)
+# end
+# 
+# desc "Run the specs under spec/"
+# Spec::Rake::SpecTask.new do |t|
+#   t.spec_opts = ['--options', "spec/spec.opts"]
+#   t.spec_files = FileList['spec/**/*_spec.rb']
+# end

data/vendor/daemon-kit/Configuration.txt

@@ -0,0 +1,102 @@
+= Configuring your daemon
+
+daemon-kit provides a multitude of ways to configure your daemon, this document
+will outline the different options available to you.
+
+== Configuration files and #DaemonKit::Config
+
+#DaemonKit::Config gives you easy access to any YAML configuration
+files you have in your <em>config</em> directory.
+
+You can access the configuration files like this:
+
+  config = DaemonKit::Config.load('sample')
+
+The above snippet relies on the presence of a <em>config/sample.yml</em> file.
+
+#DaemonKit::Config is environment aware, so configuration files are
+parsed for a top-level key that is the same as the value of
+<em>DAEMON_ENV</em>, and if present is loaded into the object as the
+configuration data. If the key is not present, the whole YAML
+document is exposed as configuration data.
+
+== Command line arguments
+
+The most flexible way to configure your daemon is through command line
+arguments, or switches.
+
+DaemonKit includes a couple of its own arguments that can be used:
+
+  -e ENV (or --env ENV) to set the daemon environment
+  --pid /path/to/pidfile to set the path to a pidfile
+  -l path (or --log path) to set the path for the log file
+  -v shows the DaemonKit version
+  -h shows a useful help message
+
+=== Custom arguments
+
+It is possible for you to specify your own arguments as well, by
+updating the <em>config/arguments.rb</em> file. This file is eval'd
+inside #DaemonKit::Arguments and gives you access to the following two
+variables:
+
+* opts - Instance of OptionParser[http://www.ruby-doc.org/stdlib/libdoc/optparse/rdoc/classes/OptionParser.html]
+* @options - A standard Ruby hash that you can populate and access later
+
+Your custom arguments can be accessed like this:
+
+  DaemonKit.arguments.options
+
+=== Advanced Configuration
+
+All the writable attributes of the default #DaemonKit::Configuration
+instance call also be modified from the command line using the special
+<em>--config</em> arguments:
+
+  --config force_kill_wait=30
+
+This happens after <em>config/environment.rb</em> is processed, so all
+command line arguments will overwrite those values.
+
+=== Daemon umask
+
+By default daemon processes run with a umask of 022, but this can be changed
+on the command line or in +config/environment.rb+.
+
+To set a more restrictive umask via command line arguments, you can start your
+daemon like this:
+
+  $ ./bin/daemon start --config umask=0077
+
+Or the same in +config/environment.rb+
+
+  DaemonKit::Initializer.run do |config|
+    # ...
+
+    # restrictive umask
+    config.umask = 0077
+
+    # ...
+  end
+
+=== Privilege Separation
+
+By default daemon processes run as the user that starts them, inheriting all
+their privileges (or lack thereof). Getting daemon-kit to drop privileges
+can currently only be done using command-line parameters, and only works
+reliable on *nix (OSX seemed cranky at the time of testing).
+
+  $ ./bin/daemon start --config user=nobody --config group=nobody
+
+Privileges are dropped at the earliest possible phase of starting the daemon.
+
+Things to note on privilege separation:
+
+* You generally have to be root to be able to perform this
+* File system permissions for +log/+ needs to be correct
+* Daemon-kit will only shed privileges on the +start+ command, not on +run+
+* Make sure your code is secure if accepting stuff from the outside world
+
+The implementation stems from the advice given by Joe Damato on his blog post
+http://timetobleed.com/tag/privilege-escalation/
+

data/vendor/daemon-kit/Deployment.txt

@@ -0,0 +1,113 @@
+= Deploying your daemons
+
+daemon-kit provides built-in support for
+Capistrano[http://www.capify.org] deployments, using a customized
+version of the standard 'deploy' recipe for Ruby on Rails
+applications.
+
+User of Vlad[http://hitsquad.rubyforge.org/vlad/]? Get in touch so we
+can discuss your contribution to daemon-kit ;)
+
+== Generating capistrano configurations
+
+When generating a new daemon, you can pass the <em>-d capistrano</em>
+argument to the <em>daemon_kit</em> command. In case you already have
+a generated daemon, run the following command inside your project:
+
+  $ ruby script/generate deploy_capistrano
+
+== Overview of generated configurations
+
+The generator creates the following files worth noticing:
+
+  config/deploy.rb
+  config/deploy/*.rb
+
+The generator also creates a new environment for you, a
+<em>staging</em> environment. Useful for testing your deployments
+before taking anything into production.
+
+== Configuring capistrano
+
+For each environment (staging & production) you only need to specify
+the target hosts in <em>config/deploy/(staging|production).rb</em>.
+
+Each of the stub files have example configuration values you can just
+edit.
+
+The rest of your configuration generally occurs in
+<em>config/deploy.rb</em>.
+
+Everything works exactly like standard capistrano, with the exception
+of the following directives:
+
+* :config_files
+* :shared_children
+
+=== :config_files
+
+Since the daemon configuration files will almost always differ between
+your development environment and your staging/production environment,
+the deployment recipe makes adequate provision for this.
+
+Use the :config_files directive to set an array of file names from the
+<em>config</em> directory that you want replaced with production
+configuration files found on the server:
+
+  set :config_files, %w{ amqp.yaml }
+
+On your target server, in the <em>:deploy_to</em> folder, create a
+<em>config</em> directory and place your configuration files in
+there. One each deploy, capistrano will rename the files in your
+deployed configuration directory with a <em>.orig</em> extension, and copy
+the files from <em>:deploy_to/config</em> into the newly deployed
+release.
+
+This makes it easy to keep production configurations out of your
+working directories or version control systems.
+
+=== :shared_children
+
+The original capistrano recipe that daemon-kit's recipe is built from
+provided support for tracking shared directories between
+deployments. This works by removing the deployed directory, and
+creating a symlink from <em>:deploy_to/shared/</em> into the correct
+location within the deployed release.
+
+You specify your list of directories with the
+<em>:shared_children</em>, each being relative to the DAEMON_ROOT.
+
+  set :shared_children, %w{ log }
+
+The daemon-kit deployment recipe makes no assumptions on shared
+directories, and gives you full control. The default only includes the
+log directory, which you can remove if you want separate log
+directories for each deployed release.
+
+== Remote dependencies
+
+By default, the deployment configuration file is configured to check
+the remote dependencies before updating the code on the target
+host. You can disable this behaviour by commenting out the following
+line:
+
+  before "deploy:update_code", "deploy:check"
+
+The only default remote dependency is the daemon-kit gem, and it will
+check for the same version you currently have installed (or a later
+one).
+
+== More capistrano resources
+
+To see a list of available commands, please run the following command
+in the root of your project:
+
+  $ cap -vT
+
+For more information on capistrano, please refer to the following list
+of online resources:
+
+* Capistrano Website[http://www.capify.org]
+* Capistrano Wiki[http://wiki.capify.org]
+* Capistrano Group[http://groups.google.com/group/capistrano]
+* #capistrano on Freenode

data/vendor/daemon-kit/History.txt

@@ -0,0 +1,97 @@
+== 0.1.7.10 (WIP)
+
+* Ruote remote participants
+* Allow process umask to be configured, defaults to 022
+* Updates to DaemonKit::Config hashes
+* Fixed argument parsing bug (reported by Mathijs Kwik (bluescreen303)
+* Support for privilege separation (See Configuration.txt)
+
+== 0.1.7.9 2009-06-22
+
+* Backtraces only logged on unclean shutdown
+* AMQP generator got new keep alive code
+
+== 0.1.7.8 2009-06-22
+
+* Optional logging of all exceptions when the daemon process dies
+  unexpectedly
+* Update generated environment.rb to reflect new backtraces option
+
+== 0.1.7.7 2009-06-22
+
+* Fixed compatibility with rufus-scheduler-2.0.0 (or newer) in cron
+  generator
+* Started central eventmachine reactor management code
+* Now depends on eventmachine
+
+== 0.1.7.6 (Not released)
+
+* Support for cucumber
+* Fixed issue in daemon_kit:upgrade task
+* Moved rspec generator into new home
+* Removed conflicting rubigen generator, messed with our script directory
+* Fixed bug where environment.rb overwrites some --config values (reported by Josh Owens)
+
+== 0.1.7.5 2009-06-08
+
+* New AbstractLogger
+** Default Logger backend
+** SysLogLogger support
+* More documentation
+
+== 0.1.7.4 2009-06-05
+
+* Fixed bug with control script generator (thanks Sho Fukamachi)
+* Enhanced deploy.rb template to check for current dk gem verion,
+  unless vendored
+* Fix bug in capistrano recipe for restarting daemons
+* Added log:truncate rake task
+* Error mails now handled by TMail
+
+== 0.1.7.3 2009-05-31
+
+* Removed dependency on daemons gem, now handled in house
+* New argument management
+* Some more docs
+
+== 0.1.7.1 2009-05-28
+
+* Fixed some minor issue with Capistrano support
+* Added support for generating dog/monit configuration files via rake
+* Initial implementation of ./script/* utilities
+
+== 0.1.7 2009-05-26
+
+* Capistrano deployment support
+
+== 0.1.6 2009-05-13
+
+* DaemonKit::Safety class to handle the trapping and logging of
+  exceptions, as well as email notifications or Hoptoad notifications.
+* New config/pre-daemonize and config/post-daemonize structure
+* New tasks to simplify upgrading daemon-kit projects
+* Fixed some other annoyances and bugs
+* Bigger TODO list
+
+== 0.1.5 2009-05-07
+
+* DaemonKit::Config class to easy the use of YAML configs internally,
+  and in generated daemons
+
+== 0.1.2 2009-04-28
+
+* Added missing rubigen dependency
+
+== 0.1.1 2009-04-27
+
+* AMQP consumer generator added
+* 'cron' style generator added
+* Allow configuring dir_mode and dir (pid file location) (Jim Lindley)
+
+== 0.1.0 2009-01-08
+
+* Ability to freeze the gem/edge copies of DaemonKit
+* Simple non-evented Jabber generator
+* Flexible UNIX signal trapping configuration
+* Basic generator completed
+* 1 small step for man, 1 giant leap for mankind