yabeda-rails 0.1.1 → 0.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: aa7de0e49e6d7ec219880b9cac720b691118fe263ad5cdac3400627f82e35409
-  data.tar.gz: 0b220d9d05316e537622d9eba39f26fb1570e7b5979817b8dce05f172c3b5039
+  metadata.gz: fa6080838a84371c2f8b813d8f2e613f15dbdddeb2c4281b63eff6368a26aae0
+  data.tar.gz: bba458511569e406752c603e5d897415227dac7edb84c58ae80148c88beaa352
 SHA512:
-  metadata.gz: bdce37215d1e3f562018d011fa446492587bbc4cabb694db9d73d7d7056c73e4b4e64aff3bd11dfdcec0dbe2024da8f587ab5f7cde988de721aab0b834b95cd3
-  data.tar.gz: 13bbdce6455f6b5af379034f895809320f585ecb144906837a01e06e23477ff767e26f538249d833201a088a33f42f588248a42dfe39d1e01c74462b3781dfac
+  metadata.gz: 3df4bbd07f750e0d32d6b84a894ac74c130fc64844dce69bd8ad9b3e445f7ca61972308528ebadd78d4a0b67198199b203e7b9b881f37ef0d8baae06baac2fb4
+  data.tar.gz: 41dd0f1141cd22e182b2e0c4461a712aa1ecb9de97d233b4b03d726345c93c82cb863c1b1752525d05d4e0195d1d3486a0bd9f43c5567eb7ae9fd824407fcf40

data/CHANGELOG.md

@@ -0,0 +1,25 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
+and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
+
+
+## 0.1.2 - 2019-01-19
+
+### Added
+
+ - Support for Puma application server. @daffydowden
+
+## 0.1.1 - 2018-10-17
+
+### Changed
+
+ - Renamed evil-metrics-rails gem to yabeda-rails. @Envek
+
+## 0.1.0 - 2018-10-03
+
+ - Initial release of evil-metrics-rails gem. @Envek
+
+   Basic metrics for request durations by controller, action, status, format, and method. ActiveRecord and ActionView timings.

data/README.md

@@ -18,6 +18,23 @@ And then execute:
 
     $ bundle
 
+### Registering metrics on server process start
+
+Currently, yabeda-rails automatically registers rails metrics when a server is started via `rails server` or `puma -C config/puma.rb`. However, other application servers or launching via `rackup` aren't supported at the moment.
+
+A possible workaround is to detect server process and manually activate yabeda-rails in an initializer:
+
+```ruby
+# config/initializers/yabeda.rb
+
+if your_app_server_process? # Your logic here
+  Yabeda::Rails.install!
+end
+```
+
+You always can add support for your app server to [lib/yabeda/rails/railtie.rb](). Pull Requests are always welcome!
+
+
 ## Metrics
 
  - Total web requests received: `rails_requests_total`

data/lib/yabeda/rails/railtie.rb

@@ -4,10 +4,18 @@ module Yabeda
   module Rails
     class Railtie < ::Rails::Railtie # :nodoc:
       config.after_initialize do
-        next unless ::Rails.const_defined?(:Server)
+        next unless rails_server? || puma_server?
 
         ::Yabeda::Rails.install!
       end
+
+      def rails_server?
+        ::Rails.const_defined?(:Server)
+      end
+
+      def puma_server?
+        ::Rails.const_defined?('Puma::CLI')
+      end
     end
   end
 end

data/lib/yabeda/rails/version.rb

@@ -2,6 +2,6 @@
 
 module Yabeda
   module Rails
-    VERSION = "0.1.1"
+    VERSION = "0.1.2"
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: yabeda-rails
 version: !ruby/object:Gem::Version
-  version: 0.1.1
+  version: 0.1.2
 platform: ruby
 authors:
 - Andrey Novikov
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2018-10-17 00:00:00.000000000 Z
+date: 2019-01-19 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: yabeda
@@ -91,6 +91,7 @@ files:
 - ".rspec"
 - ".rubocop.yml"
 - ".travis.yml"
+- CHANGELOG.md
 - Gemfile
 - LICENSE.txt
 - README.md
@@ -120,8 +121,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project: 
-rubygems_version: 2.7.6
+rubygems_version: 3.0.1
 signing_key: 
 specification_version: 4
 summary: Extensible metrics for monitoring Ruby on Rails application