flyingmachine-merb_whoops_notifier 1.0.1 → 1.0.2

data/README

@@ -1,31 +1,18 @@
 merb_whoops_notifier
 ---------------------------------------------
-This is merb plugin for exception notification with whoops. It should work with
+This is merb plugin for exception notification with Whoops. It should work with
 any merb app that's based on merb 1.0 and higher
 
-This plugin: http://github.com/atmos/merb_whoops_notifier/tree/master
-The original: http://github.com/thoughtbot/whoops_notifier/tree/master
+This plugin: http://github.com/flyingmachine/merb_whoops_notifier/tree/master
+The original: http://github.com/atmos/merb_hoptoad_notifier/tree/master
 
 Usage:
 
-1) Get your api key for your app from whoopsapp.com
+1) Get Whoops (http://github.com/flyingmachine/whoops/tree/master) and set it up
 
-2) Add the api key to config/whoops.yml with a similar syntax as the following
----
-:development: &defaults
-  :api_key: ZOMGLOLROFLMAO
+2) Copy whoops.yml.example to the config directory of your merb app and modify it
 
-:rake:
-  <<: *defaults
-
-:test:
-  <<: *defaults
-
-:production:
-  :api_key: UBERSECRETSHIT
-
-
-3) Require whoops in init.rb
+3) Require this gem in dependencies.rb
 require 'merb_whoops_notifier'
 
 4) Add the following method to your Exceptions controller.  Depending on your merb version you'll need to use the exceptions,standard_error, or internal_server error as the action name.  Kinda weak, but the API changed a lot in 0.9.x
@@ -39,11 +26,12 @@ class Exceptions < Merb::Controller
   end
 end
 
-5) Restart the server, trigger an error(in staging or prod) and check that it arrived at whoops :)
+5) Restart the server, trigger an error (in staging or prod) and check that it arrived at your Whoops server :)
 
 
 Filtersing your post environment
 --------------------------------
+# This feature hasn't been tested
 If you have environmental variables set in your ruby process that should not be sent to whoops,
 there's a mechanism for filtering those attributes now.  Throw something like this in 
 config/init.rb
@@ -54,6 +42,5 @@ end
 
 Each of these words will be compiled into a regex so you should be able to use anchors if needed.
 
-Thanks to the following GitHubbers
-----------------------------------
-joakimk, fairchild and cv.
+--------------------------------
+Thanks to atmos for the original merb_hoptoad_notifier plugin

data/lib/merb_whoops_notifier/whoops_notifier.rb

@@ -36,7 +36,7 @@ module WhoopsNotifier
       }
 
       data[:environment] = clean_whoops_environment(ENV.to_hash.merge(request.env))
-      data[:environment][:RAILS_ENV] = Merb.env
+      data[:environment][:app_env] = Merb.env
 
       data[:session] = {
          :key         => session.instance_variable_get("@session_id"),

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: flyingmachine-merb_whoops_notifier
 version: !ruby/object:Gem::Version 
-  version: 1.0.1
+  version: 1.0.2
 platform: ruby
 authors: 
 - Daniel Higginbotham