econfig-keychain 1.0.2 → 2.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 8510be80ac12c816ca31d78e99966ed7e7239f48
-  data.tar.gz: 17623f293d5e9d461cf910c7d30f63dd955c3d52
+  metadata.gz: 470f3d19f1db3d9779d0bf035cfe902f84fa90c5
+  data.tar.gz: c42eac479ba18c06ab08d9d79a38a3cb3ecd8be4
 SHA512:
-  metadata.gz: c99c777e3f184bb88509dc28d366e9fbaea0af8271625f7a281325d2da474d32c017f28e9204c3524f2d26545a7372adc8dfc39d03ad5d261f18492bf8639e7a
-  data.tar.gz: f2a97f4e6e69865ba0320c62c7794d88d87ce95d5d5d8e4885b900664df553366edb04b1e5a9c921e67f9b8bf93c03508b164e056c3c5bccf83f66bfb7595bb7
+  metadata.gz: c55059239ed39bc3051103bdc747974bc41513411a9baadea0b7b7914aa139352bc8012c62d4823674b94e48afb8c7977214abb7efb6cc32cf9cc4d40c3403f2
+  data.tar.gz: 58d3947d41a0670dcb6c6f76b37bd1178fd23bd9b8b641e50cbf108d86fd31ccf8849cb3f1dde18e38f7912ccc73e9fda3905c69c2ff3f1de339753a5564617e

data/README.md

@@ -17,13 +17,16 @@ Second, create a keychain you wish to store configuration in, name it something
 clever like `thanks-a-latte`. Within `config/application.rb` write the following:
 
 ``` ruby
-# … some rails setup previously
 module MyApp
   extend Econfig::Shortcut
-  Econfig.use_keychain "thanks-a-latte" if Rails.env.development?
-  
+
+  if Rails.env.development?
+    Econfig.backends.use :keychain, Econfig::Keychain.new("thanks-a-latte")
+  end
+
   class Application < Rails::Application
-  # … rest of the configuration
+    # … rest of the configuration
+  end
 ```
 
 That's it!
@@ -31,7 +34,7 @@ That's it!
 Econfig::Keychain will automatically create an empty secure note using the name of the directory your project is located at, in the `thanks-a-latte` keychain. If you wish to specify the name yourself, you can do so:
 
 ``` ruby
-Econfig.use_keychain "thanks-a-latte", name: "project name"
+Econfig.backends.use :keychain, Econfig::Keychain.new("thanks-a-latte", name: "project name")
 ```
 
 ## Changing configuration
@@ -39,7 +42,7 @@ Econfig.use_keychain "thanks-a-latte", name: "project name"
 Econfig::Keychain supports changing configuration by setting values, e.g. from the Rails console:
 
 ``` ruby
-MyApp.aws_access_key_id = "xyz"
+MyApp.config[:keychain, :aws_access_key_id] = "xyz"
 ```
 
 You can also edit your configuration with your `$EDITOR` manually using the Mellon CLI:

data/econfig-keychain.gemspec

@@ -19,7 +19,7 @@ Gem::Specification.new do |spec|
 
   spec.required_ruby_version = "~> 2.0"
 
-  spec.add_dependency "econfig"
+  spec.add_dependency "econfig", "~> 1.0"
   spec.add_dependency "mellon", "~> 1.0"
 
   spec.add_development_dependency "bundler", "~> 1.6"

data/lib/econfig/keychain/version.rb

@@ -1,5 +1,5 @@
 module Econfig
   class Keychain
-    VERSION = "1.0.2"
+    VERSION = "2.0.0"
   end
 end

data/lib/econfig-keychain.rb

@@ -1,9 +1 @@
 require "econfig/keychain"
-
-module Econfig
-  class << self
-    def use_keychain(keychain, **kwargs)
-      Econfig.instance.backends << Econfig::Keychain.new(keychain, **kwargs)
-    end
-  end
-end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: econfig-keychain
 version: !ruby/object:Gem::Version
-  version: 1.0.2
+  version: 2.0.0
 platform: ruby
 authors:
 - Kim Burgestrand
@@ -9,22 +9,22 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-04-30 00:00:00.000000000 Z
+date: 2014-05-26 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: econfig
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '0'
+        version: '1.0'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '0'
+        version: '1.0'
 - !ruby/object:Gem::Dependency
   name: mellon
   requirement: !ruby/object:Gem::Requirement
@@ -128,3 +128,4 @@ summary: An OSX keychain adapter for Econfig.
 test_files:
 - spec/econfig/keychain_spec.rb
 - spec/econfig/osx.keychain
+has_rdoc: