dotenv-rails 3.0.0.beta → 3.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 84017f2c53d971b597af22f799cab58020ad0b76336fe82469dcd702e36173d9
-  data.tar.gz: c7511d8dce62e068cd518c857f913df66bccbd13dde70b9ff73279f4637eb1d3
+  metadata.gz: 8f2b607facc1a9f8b32394eb625956f2f23e448b7bc812f5047218d702355792
+  data.tar.gz: 33452c26ed90e436cf4c4df6fdb8f91f3d0ba671cd5a3187e05c63996aaf7532
 SHA512:
-  metadata.gz: ac03c442d9b507484044c2674e2705df3d9ce852a1cc22b1c8d34ce6042cdd8bd0221163847767bc5f3de9b97db59cfceb67e2b09c7c123d090ea921603aa707
-  data.tar.gz: cee6b5d3693c43e9a54ad6ab06e493174ffc68f6ef7bc892b067f0b46066a369bb563af675b028fb59cd4908e4d9c192c43ac9eafdd962c80525db344398c4b5
+  metadata.gz: f212654ed9af1e5a0f634a6e98736e2d0880e7a3f084d3d15e00df47c7cf4cfd863d0ec5b53b248c3f4daf65eb422ff714091335013dcd7b50ffadd0f2110b51
+  data.tar.gz: 1ab95d0679eb1e99a1f8144b4e883659095ce63b368dbead49e51e24781eba66b72e05a856f6138c0c205abc1afaffe9574cdf02e12f8bccd367edb68730e8b6

data/README.md

@@ -56,9 +56,9 @@ Dotenv.load('file1.env', 'file2.env')
 
 ## Autorestore in tests
 
-Since 3.0, dotenv in a Rails app will automatically restore `ENV` to its original state before each test. This means you can modify `ENV` in your tests without fear of leaking state to other tests. It works with both `ActiveSupport::TestCase` and `Rspec`.
+Since 3.0, dotenv in a Rails app will automatically restore `ENV` after each test. This means you can modify `ENV` in your tests without fear of leaking state to other tests. It works with both `ActiveSupport::TestCase` and `Rspec`.
 
-To disable this behavior, set `config.dotenv.autorestore = false` in `config/application.rb` or `config/environments/test.rb`.
+To disable this behavior, set `config.dotenv.autorestore = false` in `config/application.rb` or `config/environments/test.rb`. It is disabled by default if your app uses [climate_control](https://github.com/thoughtbot/climate_control) or [ice_age](https://github.com/dpep/ice_age_rb).
 
 To use this behavior outside of a Rails app, just `require "dotenv/autorestore"` in your test suite.
 
@@ -107,11 +107,59 @@ gem 'gem-that-requires-env-variables'
 
 ### Customizing Rails
 
-Dotenv will load the following files depending on `RAILS_ENV`, with the last file listed having the highest precedence:
+Dotenv will load the following files depending on `RAILS_ENV`, with the first file having the highest precedence, and `.env` having the lowest precedence:
+
+<table>
+  <thead>
+    <tr>
+      <th>Priority</th>
+      <th colspan="3">Environment</th>
+      <th><code>.gitignore</code>it?</th>
+      <th>Notes</th>
+    </tr>
+    <tr>
+      <th></th>
+      <th>development</th>
+      <th>test</th>
+      <th>production</th>
+      <th></th>
+      <th></th>
+    </tr>
+  </thead>
+  <tr>
+    <td>highest</td>
+    <td><code>.env.development.local</code></td>
+    <td><code>.env.test.local</code></td>
+    <td><code>.env.production.local</code></td>
+    <td>Yes</td>
+    <td>Environment-specific local overrides</td>
+  </tr>
+  <tr>
+    <td>2nd</td>
+    <td><code>.env.local</code></td>
+    <td><strong>N/A</strong></td>
+    <td><code>.env.local</code></td>
+    <td>Yes</td>
+    <td>Local overrides</td>
+  </tr>
+  <tr>
+    <td>3rd</td>
+    <td><code>.env.development</code></td>
+    <td><code>.env.test</code></td>
+    <td><code>.env.production</code></td>
+    <td>No</td>
+    <td>Shared environment-specific variables</td>
+  </tr>
+  <tr>
+    <td>last</td>
+    <td><code>.env</code></td>
+    <td><code>.env</code></td>
+    <td><code>.env</code></td>
+    <td><a href="#should-i-commit-my-env-file">Maybe</a></td>
+    <td>Shared for all environments</td>
+  </tr>
+</table>
 
-* **development**: `.env`, `.env.development`, `.env.local`, `.env.development.local`
-* **test**: `.env`, `.env.test`, `.env.test.local` - Note that it will **not** load `.env.local`.
-* **development**: `.env`, `.env.production`, `.env.local`, `.env.production.local`
 
 These files are loaded during the `before_configuration` callback, which is fired when the `Application` constant is defined in `config/application.rb` with `class Application < Rails::Application`. If you need it to be initialized sooner, or need to customize the loading process, you can do so at the top of `application.rb`
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: dotenv-rails
 version: !ruby/object:Gem::Version
-  version: 3.0.0.beta
+  version: 3.0.1
 platform: ruby
 authors:
 - Brandon Keepers
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2024-01-25 00:00:00.000000000 Z
+date: 2024-02-14 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: dotenv
@@ -16,14 +16,14 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 3.0.0.beta
+        version: 3.0.1
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 3.0.0.beta
+        version: 3.0.1
 - !ruby/object:Gem::Dependency
   name: railties
   requirement: !ruby/object:Gem::Requirement