dotenv-rails 3.1.0 → 3.1.4

Sign up to get free protection for your applications and to get access to all the features.
Files changed (3) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +2 -2
  3. metadata +5 -5
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 9bd07b59cb6784e40004515930198cd245eef51961817b42e85536dbc0ecbb9c
4
- data.tar.gz: e626c7c46b97d40188145705dac4dec25d968ee70af0010db6fcc3125a74fe66
3
+ metadata.gz: eba2694209a31b0b2814be87609f7d2b9ade6f9c6cf503fcde5a09d5a0039c9c
4
+ data.tar.gz: f28ce118c3daac8f86cc8dd23070c978ea4707517805fbd6126c4cf9bca8d18e
5
5
  SHA512:
6
- metadata.gz: bd525c23f57a04807b75b384483a6d9ddd9ea7706d11d2b398e265633a2917417e9deb4726baeb100ded9bff9a854b5d9e28b1fdb2df40d434434c1388f9bc55
7
- data.tar.gz: 5d3c70c8f52a4d1f22c302e98294736d6a27b894e777e9751ff4ae32360918893b8a2c4a3e3ab24dd0d91de1e2798cc118097489757fb66c5b73122078a4b1a3
6
+ metadata.gz: 2d9565269f3b6e969538aa1548eec1d15dc222919c5c5e786b196041c3582016bfed37df70d937fd91dffc5e5444a088c25e3c17dd57ee3c65c0decd4740ac18
7
+ data.tar.gz: 0a31c509dc21db204f07c82cecb4f8e2912fccfcda0d30f238b33d6c0e87cd778de61cc951c69bd5dd5175b4f35988292db4c4e3084cee81732de1680418df42
data/README.md CHANGED
@@ -180,7 +180,7 @@ end
180
180
  Available options:
181
181
 
182
182
  * `Dotenv::Rails.files` - list of files to be loaded, in order of precedence.
183
- * `Dotenv::Rails.overwrite` - Overwrite exiting `ENV` variables with contents of `.env*` files
183
+ * `Dotenv::Rails.overwrite` - Overwrite existing `ENV` variables with contents of `.env*` files
184
184
  * `Dotenv::Rails.logger` - The logger to use for dotenv's logging. Defaults to `Rails.logger`
185
185
  * `Dotenv::Rails.autorestore` - Enable or disable [autorestore](#autorestore-in-tests)
186
186
 
@@ -276,7 +276,7 @@ You can use the `-t` or `--template` flag on the dotenv cli to create a template
276
276
  ```console
277
277
  $ dotenv -t .env
278
278
  ```
279
- A template will be created in your working directory named `{FINAME}.template`. So in the above example, it would create a `.env.template` file.
279
+ A template will be created in your working directory named `{FILENAME}.template`. So in the above example, it would create a `.env.template` file.
280
280
 
281
281
  The template will contain all the environment variables in your `.env` file but with their values set to the variable names.
282
282
 
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: dotenv-rails
3
3
  version: !ruby/object:Gem::Version
4
- version: 3.1.0
4
+ version: 3.1.4
5
5
  platform: ruby
6
6
  authors:
7
7
  - Brandon Keepers
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2024-02-27 00:00:00.000000000 Z
11
+ date: 2024-09-18 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: dotenv
@@ -16,14 +16,14 @@ dependencies:
16
16
  requirements:
17
17
  - - '='
18
18
  - !ruby/object:Gem::Version
19
- version: 3.1.0
19
+ version: 3.1.4
20
20
  type: :runtime
21
21
  prerelease: false
22
22
  version_requirements: !ruby/object:Gem::Requirement
23
23
  requirements:
24
24
  - - '='
25
25
  - !ruby/object:Gem::Version
26
- version: 3.1.0
26
+ version: 3.1.4
27
27
  - !ruby/object:Gem::Dependency
28
28
  name: railties
29
29
  requirement: !ruby/object:Gem::Requirement
@@ -81,7 +81,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
81
81
  - !ruby/object:Gem::Version
82
82
  version: '0'
83
83
  requirements: []
84
- rubygems_version: 3.5.3
84
+ rubygems_version: 3.5.16
85
85
  signing_key:
86
86
  specification_version: 4
87
87
  summary: Autoload dotenv in Rails.