envkey 1.0.0 → 1.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 0423eb22082c5f775c25c56686eb943f899e6aba
-  data.tar.gz: ac0d7784f49ac0ccc5688b0afa23e35dead9d829
+  metadata.gz: ee093a7ca1967322db09090bc8ee1c980d7fcf07
+  data.tar.gz: aa01b9820edb3e8fe35883184f3d5f6e3e6f83a9
 SHA512:
-  metadata.gz: 8963f13406a5ac9fa0e66b924d4680ba4273d2b177b72b2aadf07f68e13b943a1d19633b3c82b6e6ba7deb3ee995fe636fa878f6e558e39749ad908edb5c7a74
-  data.tar.gz: a8a46cf837becd6f9bbd44126dff6b972b8d12ef72522aaeefd00f9128280ee14378a13ee904a251f134e09ed9fbf9683846e6302301c05266e37845993a6032
+  metadata.gz: c3be05d7fc4f20b8fd6e12fa8ac90d78523a423c952df083875eedfe157f389450bca71ad26ca5dc0608835ddcc64f9b90fa3bca979a6bbd0335fe9f03a212de
+  data.tar.gz: a75173aea4ad5488ae2552f8e27586de938c7111fa58529a02e1874d36b57b9909aaa8adc79ffc76e4897bce4f4d668ba78417d3378210cb66409269af655c25

data/README.md

@@ -1,4 +1,4 @@
-# envkey
+# envkey gem
 
 Integrate [EnvKey](https://www.envkey.com) with your Ruby or Ruby On Rails projects to keep api keys, credentials, and other configuration securely and automatically in sync for developers and servers.
 
@@ -7,12 +7,12 @@ Integrate [EnvKey](https://www.envkey.com) with your Ruby or Ruby On Rails proje
 In your Gemfile:
 
 ```ruby
-gem install 'envkey'
+gem 'envkey'
 ```
 
 If you're using Rails, that's all you need. In plain Ruby, you need to require envkey at the entry point of your application.
 
-```
+```ruby
 require 'envkey'
 ```
 
@@ -45,7 +45,7 @@ Stripe.api_key = ENV.fetch("STRIPE_SECRET_KEY")
 
 Now `STRIPE_SECRET_KEY` will stay automatically in sync for all the developers on your team.
 
-On your servers, set the `ENVKEY` as an environment variable instead of putting it in a `.env` file.
+For a server, generate a server `ENVKEY` in the EnvKey App, then set the `ENVKEY` as an environment variable instead of putting it in a `.env` file.
 
 Now your servers will stay in sync as well. If you need to rotate your `STRIPE_SECRET_KEY` you can do it in a few seconds in the EnvKey App, restart your servers, and you're good to go. All your team's developers and all your servers will have the new value.
 
@@ -57,6 +57,8 @@ The envkey gem will not overwrite existing environment variables or additional v
 
 The envkey gem caches your encrypted config in development so that you can still use it while offline. Your config will still be available (though possibly not up-to-date) the next time you lose your internet connection. If you do have a connection available, envkey will always load the latest config. Your cached encrypted config is stored in `$HOME/.envkey/cache`
 
+For caching purposes, the gem assumes you're in development mode if either `ENV["RAILS_ENV"]` or `ENV["RACK_ENV"]` is `"development"` or `"test"`. If you aren't using Rails or Rack, then it's assumed you're in development mode when a `.env` file exists in the root of your project.
+
 ## Further Reading
 
 For more on EnvKey in general:

data/lib/envkey/fetch.rb

@@ -10,7 +10,8 @@ module Envkey::Fetch
   def self.is_dev
     dev_vals = %w(development test)
     dev_vals.include?(ENV["RAILS_ENV"]) ||
-    dev_vals.include?(ENV["RACK_ENV"])
+      dev_vals.include?(ENV["RACK_ENV"]) ||
+      (ENV["RAILS_ENV"].nil? && ENV["RACK_ENV"].nil? && File.exist?(".env"))
   end
 
 end

data/lib/envkey/version.rb

@@ -1,4 +1,4 @@
 module Envkey
-  VERSION = "1.0.0"
+  VERSION = "1.0.1"
   ENVKEY_FETCH_VERSION="1.0.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: envkey
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.0.1
 platform: ruby
 authors:
 - Dane Schneider
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2017-09-23 00:00:00.000000000 Z
+date: 2017-10-05 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler