dotenv-rails 2.7.2 → 2.7.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3a8af6cf2a46cf58d3ed9539302fc11c5a217ae0e498571bf73943f0099ec6d7
-  data.tar.gz: 64adfc0c903ad99223736e1dc5a4f28651a010aa74e3ec3c6d8f9fe0e728fe95
+  metadata.gz: d0df0bf40def6cddae1b3a3f00f8e62d126a3f0cf1c2bdd7a088f8d9828732f1
+  data.tar.gz: c4c7e734b53510171eaf5e1146c49284f384efff0d89effb85579168fd249274
 SHA512:
-  metadata.gz: b73b7abe3a6e9a0d631bee1d96008f9e50fa2a97172611c4c7e53e2ffa30522f602b3a60499d87006dbbfde7f08b8de899773b71a900d28881074340fb5b7792
-  data.tar.gz: 83157159e95b2531579f3bb3b8a340164189542d996394352c15fbd66c5410ad1f73b6013a0596305a9ebd4be108ad56d4631e00090bfd9515a908e20763ffb4
+  metadata.gz: 2ba04b9211d3137e4bf6691cf0d618c13d93b96ba1f908e932dbe4a0c676b690202742cd6bcec11b57a83f83cef95ce75fdb43fccfc13f79f813311103a44611
+  data.tar.gz: 617af05f7735a9c25292fcd6d592ab37f4471727299fbe04d92966130ac7345834e7c155548505de9b57b404c7690447f994c1357cd52ff00cfc68e64e57179a

data/README.md

@@ -218,6 +218,29 @@ If you use this gem to handle env vars for multiple Rails environments (developm
 
 Credentials should only be accessible on the machines that need access to them. Never commit sensitive information to a repository that is not needed by every development machine and server.
 
+
+You can use the `-t` or `--template` flag on the dotenv cli to create a template of your `.env` file.
+```shell
+$ dotenv -t .env
+```
+A template will be created in your working directory named `{FINAME}.template`. So in the above example, it would create a `.env.template` file. 
+
+The template will contain all the environment variables in your `.env` file but with their values set to the variable names.
+
+```shell
+# .env
+S3_BUCKET=YOURS3BUCKET
+SECRET_KEY=YOURSECRETKEYGOESHERE
+```
+
+Would become 
+
+```shell
+# .env.template
+S3_BUCKET=S3_BUCKET
+SECRET_KEY=SECRET_KEY
+```
+
 Personally, I prefer to commit the `.env` file with development-only settings. This makes it easy for other developers to get started on the project without compromising credentials for other environments. If you follow this advice, make sure that all the credentials for your development environment are different from your other deployments and that the development credentials do not have access to any confidential data.
 
 ### Why is it not overriding existing `ENV` variables?

data/lib/dotenv/rails.rb

@@ -9,8 +9,9 @@ require "dotenv"
 #
 # See https://github.com/bkeepers/dotenv/issues/219
 if defined?(Rake.application)
-  is_running_specs = Rake.application.top_level_tasks.grep(/^spec(:|$)/).any?
-  Rails.env = ENV["RAILS_ENV"] ||= "test" if is_running_specs
+  if Rake.application.top_level_tasks.grep(/^(parallel:spec|spec(:|$))/).any?
+    Rails.env = ENV["RAILS_ENV"] ||= "test"
+  end
 end
 
 Dotenv.instrumenter = ActiveSupport::Notifications
@@ -51,8 +52,6 @@ module Dotenv
       instance.load
     end
 
-    config.before_configuration { load }
-
     private
 
     def dotenv_files
@@ -63,5 +62,7 @@ module Dotenv
         root.join(".env")
       ].compact
     end
+
+    config.before_configuration { load }
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: dotenv-rails
 version: !ruby/object:Gem::Version
-  version: 2.7.2
+  version: 2.7.4
 platform: ruby
 authors:
 - Brandon Keepers
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2019-03-25 00:00:00.000000000 Z
+date: 2019-06-24 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: dotenv
@@ -16,14 +16,14 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 2.7.2
+        version: 2.7.4
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 2.7.2
+        version: 2.7.4
 - !ruby/object:Gem::Dependency
   name: railties
   requirement: !ruby/object:Gem::Requirement