dumper 1.2.0 → 1.2.1

data/README.md

@@ -65,3 +65,13 @@ end
 ```
 
 If you are using resque, it's a good idea to run it on the same host with Redis, and start the agent on the resque instance.
+
+## Debugging
+
+If the agent doesn't seem to work, pass `Logger::DEBUG` to the `loglevel` option.
+
+```ruby
+Dumper::Agent.start(app_key: '...', loglevel: Logger::DEBUG)
+```
+
+It gives verbose logging that helps us to understand the problem.

data/lib/dumper/agent.rb

@@ -40,8 +40,8 @@ module Dumper
     end
 
     def start
+      log "stack: #{@stack.to_hash}", :debug
       return unless @stack.supported?
-      log "stack: dispatcher = #{@stack.dispatcher}, framework = #{@stack.framework}, rackup = #{@stack.rackup}"
 
       @loop_thread = Thread.new { start_loop }
       @loop_thread[:name] = 'Loop Thread'

data/lib/dumper/version.rb

@@ -1,3 +1,3 @@
 module Dumper
-  VERSION = '1.2.0'
+  VERSION = '1.2.1'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: dumper
 version: !ruby/object:Gem::Version
-  version: 1.2.0
+  version: 1.2.1
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-08-31 00:00:00.000000000 Z
+date: 2012-09-20 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: multi_json
@@ -215,19 +215,24 @@ required_ruby_version: !ruby/object:Gem::Requirement
   - - ! '>='
     - !ruby/object:Gem::Version
       version: '0'
+      segments:
+      - 0
+      hash: 229918553143605081
 required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
   requirements:
   - - ! '>='
     - !ruby/object:Gem::Version
       version: '0'
+      segments:
+      - 0
+      hash: 229918553143605081
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.19
+rubygems_version: 1.8.24
 signing_key: 
 specification_version: 3
 summary: The Dumper Agent for Rails (coming soon!)
 test_files:
 - spec/dumper_spec.rb
 - spec/spec_helper.rb
-has_rdoc: