dotenv-rails 3.1.0 → 3.1.8

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 9bd07b59cb6784e40004515930198cd245eef51961817b42e85536dbc0ecbb9c
-  data.tar.gz: e626c7c46b97d40188145705dac4dec25d968ee70af0010db6fcc3125a74fe66
+  metadata.gz: c0e302fb028f65e97a5a1c22d97534a0fbc42fc6e84b6ba11fde5d5406dd2334
+  data.tar.gz: cc3d75dc764b994ce40ac42dabbcb89f88a611236f0122f1ae91517a752f71d9
 SHA512:
-  metadata.gz: bd525c23f57a04807b75b384483a6d9ddd9ea7706d11d2b398e265633a2917417e9deb4726baeb100ded9bff9a854b5d9e28b1fdb2df40d434434c1388f9bc55
-  data.tar.gz: 5d3c70c8f52a4d1f22c302e98294736d6a27b894e777e9751ff4ae32360918893b8a2c4a3e3ab24dd0d91de1e2798cc118097489757fb66c5b73122078a4b1a3
+  metadata.gz: dd0c122d22515d49b9c245c9ba2f4f62ebe21d60fec5e599ea521c6ddb536b3d222e09d1dd356144252c96e4d4ffd9b9a526a7d0f828807d7f588f4cb62b33d8
+  data.tar.gz: c5979568723021877ab6706d2a16a6c3ab5f274d307a25de670f5a34a486a60483a13d14ad851fa94dbce6a9505ebb36d934cb93f55e734318da08cad09a7fa8

data/README.md

@@ -2,6 +2,11 @@
 
 Shim to load environment variables from `.env` into `ENV` in *development*.
 
+<img align="left" src="https://github.com/user-attachments/assets/0052ed0b-00d2-416a-bdaa-0466c0226933" width="80" />
+<div><sup>Dotenv is proud to be <a href="https://github.com/sponsors/bkeepers">sponsored by</a>:</sup></div>
+<strong><a href="https://bit.ly/dotenv-stoked-seagull">Stoked Seagull Software</a></strong>
+<div>Need help with a software project but don't know where to begin? <a href="https://bit.ly/dotenv-stoked-seagull">Stoked Seagull can help.</a></div><br><br>
+
 Storing [configuration in the environment](http://12factor.net/config) is one of the tenets of a [twelve-factor app](http://12factor.net). Anything that is likely to change between deployment environments–such as resource handles for databases or credentials for external services–should be extracted from the code into environment variables.
 
 But it is not always practical to set environment variables on development machines or continuous integration servers where multiple projects are run. dotenv loads variables from a `.env` file into `ENV` when the environment is bootstrapped.
@@ -84,7 +89,7 @@ You can use the `dotenv` executable load `.env` before launching your applicatio
 $ dotenv ./script.rb
 ```
 
-The `dotenv` executable also accepts the flag `-f`. Its value should be a comma-separated list of configuration files, in the order of most important to least. All of the files must exist. There _must_ be a space between the flag and its value.
+The `dotenv` executable also accepts the flag `-f`. Its value should be a comma-separated list of configuration files, in the order of the most important to the least important. All of the files must exist. There _must_ be a space between the flag and its value.
 
 ```console
 $ dotenv -f ".env.local,.env" ./script.rb
@@ -180,7 +185,7 @@ end
 Available options:
 
 * `Dotenv::Rails.files` - list of files to be loaded, in order of precedence.
-* `Dotenv::Rails.overwrite` - Overwrite exiting `ENV` variables with contents of `.env*` files
+* `Dotenv::Rails.overwrite` - Overwrite existing `ENV` variables with contents of `.env*` files
 * `Dotenv::Rails.logger` - The logger to use for dotenv's logging. Defaults to `Rails.logger`
 * `Dotenv::Rails.autorestore` - Enable or disable [autorestore](#autorestore-in-tests)
 
@@ -213,7 +218,7 @@ DATABASE_URL="postgres://$(whoami)@localhost/my_database"
 
 ### Variable Substitution
 
-You need to add the value of another variable in one of your variables? You can reference the variable with `${VAR}` or often just `$VAR` in unqoted or double-quoted values.
+You need to add the value of another variable in one of your variables? You can reference the variable with `${VAR}` or often just `$VAR` in unquoted or double-quoted values.
 
 ```shell
 DATABASE_URL="postgres://${USER}@localhost/my_database"
@@ -276,7 +281,7 @@ You can use the `-t` or `--template` flag on the dotenv cli to create a template
 ```console
 $ 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.
+A template will be created in your working directory named `{FILENAME}.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.
 

metadata

@@ -1,14 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: dotenv-rails
 version: !ruby/object:Gem::Version
-  version: 3.1.0
+  version: 3.1.8
 platform: ruby
 authors:
 - Brandon Keepers
-autorequire: 
 bindir: bin
 cert_chain: []
-date: 2024-02-27 00:00:00.000000000 Z
+date: 2025-04-10 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: dotenv
@@ -16,14 +15,14 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 3.1.0
+        version: 3.1.8
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 3.1.0
+        version: 3.1.8
 - !ruby/object:Gem::Dependency
   name: railties
   requirement: !ruby/object:Gem::Requirement
@@ -65,8 +64,9 @@ files:
 homepage: https://github.com/bkeepers/dotenv
 licenses:
 - MIT
-metadata: {}
-post_install_message: 
+metadata:
+  changelog_uri: https://github.com/bkeepers/dotenv/releases
+  funding_uri: https://github.com/sponsors/bkeepers
 rdoc_options: []
 require_paths:
 - lib
@@ -81,8 +81,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.5.3
-signing_key: 
+rubygems_version: 3.6.2
 specification_version: 4
 summary: Autoload dotenv in Rails.
 test_files: []