rack-ip-authorizer 0.0.3 → 0.0.4

checksums.yaml

@@ -1,7 +1,15 @@
 ---
-SHA1:
-  metadata.gz: 7276aa411d774580759f3c27e3eb32205106da5f
-  data.tar.gz: 43e5ae7de9fb58a0ec906d7c46d7a963aebecad3
-SHA512:
-  metadata.gz: 14a09ff33288eb8b63bf7cbfeb6c12054013dd0e74bb4c522ba7fc3ea090b808d2699b68408bdd980a9aab1de783b8d8eae5ae997eabaf9c6c097f935a4a77ba
-  data.tar.gz: c2c1363f3afb39e18b023295e9d01fa73242a007e1f2501de8c49521b75dbdc0b384a51f89e17e5f84bf019f8f0364715ecf911322f46e6bff3747260fbac3c1
+!binary "U0hBMQ==":
+  metadata.gz: !binary |-
+    NzI0ZjdhZTI1NTFmYTM0ODNiNzU5ZTgwN2VlZDdlYzBmMDE2NzZmZg==
+  data.tar.gz: !binary |-
+    ZjlhNjE3MWE4ZGI2YjM5YTdjZTFkOTA2MDNmYjYwZjIwYzdjOTQ1Mw==
+!binary "U0hBNTEy":
+  metadata.gz: !binary |-
+    ODllNWZhNWM4ZjgwYTM2MWZlZWY4NzdjMDY2ZTQwZGRjZDQwODk5ZTc5ODI1
+    OGUxNTA4ZTg1OTQzODZkMTRmZjhhYTFiNGIyM2RhN2FjNmVlNWYwYmJjZmU0
+    MWNkY2UzNTNlNzAwZjdhNDFiZTMwMDNjZDFhNDcxNGZmMjY3MTA=
+  data.tar.gz: !binary |-
+    NjM4YjFkYjllODE1Y2M4ZDhkNWU1YzA3ZmQ1Y2NmN2UwMGI1ODM0NTJhNjE5
+    M2JkYzYzOWM5NGY2ODM1MjQ0MGUyMmExOTJkMmU3MTQxN2Y2OGVjZGVlNDIw
+    Y2MzMmJjNTgxODgwZjdiYTg3YmMwMTRlYTQyMWEzOGEzYWQxOGQ=

data/README.md

@@ -20,28 +20,23 @@ Or install it yourself as:
 
 ### Rails 3 apps
 
-1. Create a file named "ip_authorizations.yml" in config directory
-2. Fill it with paths (keys) and IPs (values) see example below
+1. Create an initializer defining the environment you want to watch (production by default), example:
+```ruby
+Rack::IpAuthorizer.env_to_check = ['staging','development']
+```
+2. Create a file named "ip_authorizations.yml" in config directory
+3. Fill it with paths (keys) and IPs (values) see example below
 
 ```yaml
 admin:
     - 192.168.0.1
     - 192.168.0.2
     - 192.168.0.3
-superadmin:
+monitor:
     - 192.168.0.1
     - 192.168.0.2
 ```
-
-### Environment filter
-
-Create an initializer and add:
-
-```ruby
-Rack::IpAuthorizer.env_to_check = ['staging','development']
-```
-
-Based on the file names in 'config/environments' you can use any of them including Rails defaults.
+4. According to this example, path to http://www.my-application.com/admin and http://www.my-application.com/monitor have access restricted by IP  
 
 ## Contributing
 

data/lib/rack/ip_authorizer.rb

@@ -1,8 +1,8 @@
-require "rack/version"
+require 'rack/version'
 
 module Rack
   class IpAuthorizer
-    @env_to_check = ["production"]
+    @env_to_check = ['production']
     class << self
       attr_accessor :env_to_check
     end

data/lib/rack/version.rb

@@ -1,3 +1,3 @@
 module RackIpAuthorizer
-  VERSION = "0.0.3"
+  VERSION = '0.0.4'
 end

data/lib/rack-ip-authorizer.rb

@@ -10,7 +10,7 @@ if defined? Rails
           if File.exists?(path)
             ip_authorizations_by_path = YAML.load_file(path)
           else
-            raise "config/ip_authorizations.yml is missing"
+            raise 'config/ip_authorizations.yml is missing'
           end
           app.config.middleware.insert_after(ActionDispatch::RemoteIp, Rack::IpAuthorizer, ip_authorizations_by_path)
         }

metadata

@@ -1,27 +1,27 @@
 --- !ruby/object:Gem::Specification
 name: rack-ip-authorizer
 version: !ruby/object:Gem::Version
-  version: 0.0.3
+  version: 0.0.4
 platform: ruby
 authors:
 - Thibault El Zamek, Cédric Darné, Lionel Oto
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-05-26 00:00:00.000000000 Z
+date: 2014-06-03 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rack
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '1.0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '1.0'
 - !ruby/object:Gem::Dependency
@@ -42,14 +42,14 @@ dependencies:
   name: rake
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '1.0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - '>='
+    - - ! '>='
       - !ruby/object:Gem::Version
         version: '1.0'
 - !ruby/object:Gem::Dependency
@@ -66,7 +66,8 @@ dependencies:
     - - ~>
       - !ruby/object:Gem::Version
         version: 0.6.2
-description: Basic Rack middleware for Rails 3 to authorize access to path by IP
+description: Basic Rack middleware for Rails 3 to authorize access to path by IP using
+  YML config file
 email:
 - thibault.elzamek@c4mprod.com, cedric.darne@c4mprod.com, lionel.oto@c4mprod.com
 executables: []
@@ -75,8 +76,8 @@ extra_rdoc_files: []
 files:
 - LICENSE.txt
 - README.md
-- lib/rack/version.rb
 - lib/rack/ip_authorizer.rb
+- lib/rack/version.rb
 - lib/rack-ip-authorizer.rb
 - spec/rake_ip_authorizer_spec.rb
 homepage: https://github.com/c4mprod/rack-ip-authorizer
@@ -89,20 +90,19 @@ require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>='
+  - - ! '>='
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - '>='
+  - - ! '>='
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.1.11
+rubygems_version: 2.0.8
 signing_key: 
 specification_version: 4
-summary: Basic Rack middleware for Rails 3 to authorize access to path by IP using
-  YML config file
+summary: Basic Rack middleware for Rails 3 to authorize access to path by IP
 test_files:
 - spec/rake_ip_authorizer_spec.rb