appygram-rails 1.0.2 → 1.0.3

data/.gitignore

@@ -1,8 +1,4 @@
-.ginger
-.DS_Store
-coverage
-exceptional-*.gem
-doc
-log
+*.gem
+.bundle
+Gemfile.lock
 pkg/*
-_site

data/MIT-LICENSE

@@ -1,4 +1,4 @@
-Copyright (c) 2010, Contrast.
+Copyright (C)2012 Solertium
  
 Permission is hereby granted, free of charge, to any person
 obtaining a copy of this software and associated documentation
@@ -19,4 +19,4 @@ 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.
+OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,61 @@
+# Appygram <http://www.appygram.com> - for Rails 3
+
+Appygram is a messaging service for web and mobile apps.
+
+This Gem/Plugin is for Rails applications. It will send uncaught
+exception reports (server error pages / "500 errors") to the
+Appygram trace service, which will count them and send notifications
+as appropriate.
+
+## Rails Installation
+
+1.  Add the appygram-rails gem entry to your Gemfile
+    
+    ```ruby
+    gem 'appygram-rails'
+    ```
+    
+2.  Run <code>bundle install</code>
+
+3.  Configure your API Key. If you will use Appygram in both development
+    and production, you can put it in an initializer, e.g.
+    <code>config/initializers/appygram.rb</code>. Otherwise, just put
+    it in <code>config/environments/production.rb</code>:
+    
+    ```ruby
+    Appygram.configure :api_key => 'your_api_key'
+    ```
+    
+    Use a valid API key for your app provided by Appygram.
+
+4.  A restart is required to pick up new gems and configuration.
+
+## Additional configuration
+
+To properly route messages about exception traces, you will probably
+want to at least set the default topic to some topic name configured
+in your Appygram dashboard:
+
+```ruby
+Appygram.configure :topic => 'Uncaught Exception'
+```
+
+For more configuration options, see the instructions for the core
+Appygram gem: <https://github.com/anythinglabs/appygram.rb>
+
+You can also read there about how to programmatically call Appygram
+to send user-generated messages or rescued exceptions.
+
+## Automatic devise (and similar) integration
+
+If an exception occurs within any Rails controller that responds
+to "current_user", this gem will auto-fill the "name" and "email"
+properties of the trace with the associated properties of
+current_user.
+
+## Automatic context information
+
+The current request context, including URI, parameters, and
+headers, is serialized into the app_json field of the trace.
+
+Copyright © 2012 Solertium.

data/lib/appygram-rails/integration/rack_rails.rb

@@ -12,12 +12,16 @@ module Rack
       begin
         body = @app.call(env)
       rescue Exception => e
-        ::AppygramRails::Catcher.handle_with_controller(e,env['action_controller.instance'], Rack::Request.new(env))
+        unless e.is_a? ActionController::RoutingError
+          ::AppygramRails::Catcher.handle_with_controller(e,env['action_controller.instance'], Rack::Request.new(env))
+        end
         raise
       end
 
       if env['rack.exception']
-        ::AppygramRails::Catcher.handle_with_controller(env['rack.exception'],env['action_controller.instance'], Rack::Request.new(env))
+        unless env['rack.exception'].is_a? ActionController::RoutingError
+          ::AppygramRails::Catcher.handle_with_controller(env['rack.exception'],env['action_controller.instance'], Rack::Request.new(env))
+        end
       end
 
       body

data/lib/appygram-rails/version.rb

@@ -1,3 +1,3 @@
 module AppygramRails
-  VERSION = '1.0.2'
+  VERSION = '1.0.3'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: appygram-rails
 version: !ruby/object:Gem::Version
-  version: 1.0.2
+  version: 1.0.3
   prerelease: 
 platform: ruby
 authors:
@@ -9,11 +9,11 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-11-13 00:00:00.000000000 Z
+date: 2012-11-14 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: appygram
-  requirement: &70161210414020 !ruby/object:Gem::Requirement
+  requirement: &70186041638940 !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ~>
@@ -24,10 +24,10 @@ dependencies:
         version: 1.0.3
   type: :runtime
   prerelease: false
-  version_requirements: *70161210414020
+  version_requirements: *70186041638940
 - !ruby/object:Gem::Dependency
   name: rack
-  requirement: &70161210428320 !ruby/object:Gem::Requirement
+  requirement: &70186041638260 !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ! '>='
@@ -35,7 +35,7 @@ dependencies:
         version: '0'
   type: :runtime
   prerelease: false
-  version_requirements: *70161210428320
+  version_requirements: *70186041638260
 description: appygram-rails sends uncaught Rails exceptions as traces to the hosted
   messaging service at http://www.appygram.com
 email:
@@ -46,9 +46,8 @@ extra_rdoc_files: []
 files:
 - .gitignore
 - Gemfile
-- History.txt
 - MIT-LICENSE
-- README.markdown
+- README.md
 - Rakefile
 - appygram-rails.gemspec
 - lib/appygram-rails.rb

data/History.txt

@@ -1,2 +0,0 @@
-0.1 - First version, fork documented
-Forked from Exceptional 2.0.11 (http://github.com/exceptional/exceptional) under MIT License

data/README.markdown

@@ -1,43 +0,0 @@
-# Appygram <http://www.appygram.com>
-
-Appygram is a messaging service for web and mobile apps. Among other
-things, it can accept and route exception reports.
-
-This Gem/Plugin is for Rails applications. It will route uncaught
-exception reports via Appygram.
-    
-## Rails 3 Installation
-
-1.  Add gem entry to Gemfile
-    
-    ```ruby
-    gem 'appygram-rails'
-    ```
-    
-2.  Run <code>bundle install</code>
-
-3.  Configue your API Key in an initializer, e.g. config/appygram.rb
-    
-    ```ruby
-    Appygram.configure 'your_api_key'
-    ```
-    
-    using a valid API key for your app provided by Appygram
-
-## Limiting messages
-
-This client will limit the number of exact duplicate messages it sends
-to Appygram per day. The default limit is 25 duplicates. You can adjust
-this in the initializer:
-
-```
-Appygram.set_duplicate_limit 1
-```
-
-Setting a limit of 0 will disable the duplicate check entirely.
-
-In addition to this coarse daily client-side limit, you can
-configure the number of alerts forwarded to each recipient, per
-hour, in the Appygram web console.
-
-Copyright © 2012 Anything Labs.