snappconfig 0.1.11 → 0.1.12

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: a4f441df4c6b5d5b8bc5128da26387ea3da9dc1d
-  data.tar.gz: 2dddca4c0107d723864f80dcb23d3598d7fc1f87
+  metadata.gz: b8fd70e2c0bb31207fb7217e072e1cec55bd6da6
+  data.tar.gz: 6a2fd01f719062ed424d6aca1b2c27921820c293
 SHA512:
-  metadata.gz: 7e799f7c94bf5050cdb20d881c5b1f915155395cd14a841269905e3857645c53fa068b4fa0ba3fde4509ee7306b6c14cc147df9dc4fe35b48d91bb140bdf9773
-  data.tar.gz: 7f23f25199538b84e538cec6b3c8ba026d14d091315f46c8c1a0af7c9bb47476fdb5204520d69a592ee4a3536710d29ce5fbe0e5d920c127900f4ddd9c1962d9
+  metadata.gz: 56cb2724a25c21ebd30858e7163bc59170a980148b9d148bdf299c31847f133cd9dc3f8793d035d7bb74bfbb07a4e4dce1a83daf36222c7aa1d6504e75808aa9
+  data.tar.gz: 43b6166613c9a9f654e530ac5b8145ade2797b9c29e7669940fd22293d03989cf6044d06642fd0ad4c66cbf3282464a5fcaac5730ec79b391e67044e38b72b51

data/README.md

@@ -1,18 +1,18 @@
 # Snappconfig
 
-Smarter Rails configuration that works with Heroku. Here's why it rocks:
+Smarter Rails configuration that works with Heroku:
 
-- **It's Simple**. There's no setup code. Just **add some YAML** and you're ready to roll.
-- It supports **nested values and lists**. Use the data structures you want and access them with standard hash notation (e.g. `CONFIG[:this][:that]`)
-- It promotes **secure best practices** that keep your secrets out of source control.
-- It lets you write to a nestable `CONFIG` hash *or* to  `ENV` variables- we don’t tell you how to live.
-- It's **Heroku-friendly**.
-- It's based on Ryan Bates’ excellent [Railscast](http://railscasts.com/episodes/85-yaml-configuration-revised) and inspired by [Figaro](https://github.com/laserlemon/figaro).
+- No setup code- just **add some YAML**.
+- Supports **nested values and lists**. Use the data structures you want and access them with standard hash notation (e.g. `CONFIG[:this][:that]`)
+- Promotes **secure best practices** that keep your secrets out of source control.
+- Lets you write to a nestable `CONFIG` hash *or* to  `ENV` variables.
+- **Heroku-friendly**.
+- Based on Ryan Bates’ excellent [Railscast](http://railscasts.com/episodes/85-yaml-configuration-revised) and inspired by [Figaro](https://github.com/laserlemon/figaro).
 
 ## Installation
-  
-  
-  
+
+
+
 **1)** Add it to your Gemfile and run `bundle` to install
 
     gem 'snappconfig'
@@ -35,7 +35,7 @@ To access configuration values, simply read from `CONFIG` using standard hash no
 
     token = CONFIG[:secret_token]
     stripe_secret = CONFIG[:stripe][:secret_key]
-    
+
 Or if you wrote values to `ENV`, get them the way you normally would:
 
     token = ENV['SECRET_TOKEN']
@@ -70,23 +70,23 @@ You can access `CONFIG` from anywhere in the app, including initializers and the
 
 **Nested values:**
 
-    stripe: 
+    stripe:
       publishable_key: 5883eeb3cd43cee52585
-      secret_key: 0df20bf20903c4404968 
-      
+      secret_key: 0df20bf20903c4404968
+
     development:
-      stripe: 
+      stripe:
         publishable_key: 5883eeb3cd43cee52585
         secret_key: 0df20bf20903c4404968      
     production:
-      stripe: 
+      stripe:
         publishable_key: e753e42725fe43d3994a
         secret_key: e8787290a07b1abecae9
 
 
 **ENV values:**
 
-    ENV: 
+    ENV:
         BLOG_USERNAME: "admin"
         BLOG_PASSWORD: "secret"
 
@@ -111,7 +111,7 @@ For example, the following files would be processed in order:
 ##Best practices
 
 
-There's nothing to stop you from putting all your configuration into a single `application.yml` file. However, best practices dictate that protected values like **passwords and tokens should not be stored in source control.** 
+There's nothing to stop you from putting all your configuration into a single `application.yml` file. However, best practices dictate that protected values like **passwords and tokens should not be stored in source control.**
 
 An obvious solution would be to git-ignore the config file, but that approach has its problems. Not all values need to be secret, and without any config file developers won't know what values are expected or what the defaults should be.
 
@@ -137,9 +137,9 @@ For instance, if we already have a mailer configuration that works for our app,
         authentication: 'plain'
         enable_starttls_auto: true
 
-Using the `_REQUIRED` keyword, we indicate values we expect to be included in the configuration, even though they're not in this file. 
+Using the `_REQUIRED` keyword, we indicate values we expect to be included in the configuration, even though they're not in this file.
 
-We can then fill in those values with a git-ignored file that only stores our secrets: 
+We can then fill in those values with a git-ignored file that only stores our secrets:
 
 **application.secrets.yml:**
 
@@ -148,7 +148,7 @@ We can then fill in those values with a git-ignored file that only stores our se
       smtp_settings:
         password: 8675309
 
-And there you have it- configuration without compromise!
+And there you have it- configuration without compromise
 
 The `_REQUIRED` keyword is really handy. You can use it to stub out an entire config file template. If any of the required values are not present at runtime Snappconfig will raise an error, ensuring you never go live without a complete configuration.
 
@@ -156,7 +156,7 @@ The `_REQUIRED` keyword is really handy. You can use it to stub out an entire co
 
 The Heroku file system is read-only, so if you're git-ignoring your config files you won't be able to add them in manually.
 
-But don't worry, Snappconfig provides a rake task to load your config files into Heroku. Just run:
+To fix that, Snappconfig provides a rake task to load your config files into Heroku. Just run:
 
     $ rake heroku:config:load
 
@@ -164,9 +164,7 @@ or:
 
     $ rake heroku:config:load[my_app]
 
-to target a specific app. 
-
-Slick!
+to target a specific app.
 
 
 ## Miscellaneous

data/lib/snappconfig/tasks.rake

@@ -5,19 +5,16 @@ namespace :heroku do
 
     desc "Snappconfig task to load configuration into Heroku from YAML file(s)"
     task :load, [:app] do |t, args|
+
       puts "Loading configuration files into Heroku..."
       merged_yaml = Snappconfig.merged_raw.to_yaml
       shell_yaml = Shellwords.escape(merged_yaml)
-      
+
       app_switch = args[:app] ? " --app #{args[:app]}" : ""
-      puts `heroku config:set CONFIG=#{shell_yaml}#{app_switch}`
+      # NOTE: Need to use 'Bundler.with_clean_env' instead of regular shell call
+      # in order to avoid Bundler::RubyVersionMismatch error (SEE: https://github.com/rbenv/rbenv/issues/400)
+      Bundler.with_clean_env { sh "heroku config:set CONFIG=#{shell_yaml}#{app_switch}" }
     end
 
   end
 end
-
-
-
-
-
-

data/snappconfig.gemspec

@@ -4,7 +4,7 @@ $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
 
 Gem::Specification.new do |spec|
   spec.name          = "snappconfig"
-  spec.version       = "0.1.11"
+  spec.version       = "0.1.12"
   spec.authors       = ["Yarin Kessler"]
   spec.email         = "ykessler@appgrinders.com"
   spec.summary       = %q{Smarter Rails configuration with YAML}
@@ -17,6 +17,6 @@ Gem::Specification.new do |spec|
   spec.test_files    = spec.files.grep(%r{^(test|spec|features)/})
   spec.require_paths = ["lib"]
 
-  spec.add_development_dependency "bundler", "~> 1.3"
+  spec.add_development_dependency "bundler", "~> 1.11"
   spec.add_development_dependency "rake"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: snappconfig
 version: !ruby/object:Gem::Version
-  version: 0.1.11
+  version: 0.1.12
 platform: ruby
 authors:
 - Yarin Kessler
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-04-14 00:00:00.000000000 Z
+date: 2016-06-19 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -16,14 +16,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.3'
+        version: '1.11'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.3'
+        version: '1.11'
 - !ruby/object:Gem::Dependency
   name: rake
   requirement: !ruby/object:Gem::Requirement
@@ -76,7 +76,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.0.3
+rubygems_version: 2.5.1
 signing_key: 
 specification_version: 4
 summary: Smarter Rails configuration with YAML