dotenv-rails 3.1.2 → 3.1.3

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 +7 -7
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 416f199aaf1e6db2cb942df72c55bc49b627b10f26d040200767ef35bc3dd86e
4
- data.tar.gz: 5e01fa6565c8cbc3a03e508cc5f00f706b2d60302cd6d2c60d3e5042f13b060b
3
+ metadata.gz: 3a0b16ffcfff0df077a2571ac67034f5618852220d0922d929b91a14b8bb896e
4
+ data.tar.gz: 130eba2c5e88d93ec470d3fcff682d805c7ff7b06165cc1dfd065f2af8f79d15
5
5
  SHA512:
6
- metadata.gz: db630800354dfdb320bcf6dc7e01d0f2e6e58b340130964979196c45da058977b08289dab0baa06ca7b319882d95d03e73d45872ea397f767dd01316027e6643
7
- data.tar.gz: fa1a8c6bd5e15ee7dc7e68b5f46e139e834f070573daab24823b32366ee890316ce95ebdfc8b7accc8ed5abf1ad32a41abd50f76c92b3133c7644b856c5b0e7a
6
+ metadata.gz: 2c6d26c1cc4a721373ae39c0bc47e380a79f3d718ea6e5511a7d350e26551b59a4602548e1d8180d65563af150c3ca7a8749e225f918d231ce57ef1cb2fe7e4c
7
+ data.tar.gz: 45d03123008b44dd0b5c24ed08d772bb845033a1742aa0c34198b8a5bbc13bf31908dd519dffd88c743c1aa0179feb41d227199e23dd8f37db1bf5de14f7637b
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.2
4
+ version: 3.1.3
5
5
  platform: ruby
6
6
  authors:
7
7
  - Brandon Keepers
8
- autorequire:
8
+ autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2024-05-06 00:00:00.000000000 Z
11
+ date: 2024-09-17 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.2
19
+ version: 3.1.3
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.2
26
+ version: 3.1.3
27
27
  - !ruby/object:Gem::Dependency
28
28
  name: railties
29
29
  requirement: !ruby/object:Gem::Requirement
@@ -66,7 +66,7 @@ homepage: https://github.com/bkeepers/dotenv
66
66
  licenses:
67
67
  - MIT
68
68
  metadata: {}
69
- post_install_message:
69
+ post_install_message:
70
70
  rdoc_options: []
71
71
  require_paths:
72
72
  - lib
@@ -82,7 +82,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
82
82
  version: '0'
83
83
  requirements: []
84
84
  rubygems_version: 3.5.9
85
- signing_key:
85
+ signing_key:
86
86
  specification_version: 4
87
87
  summary: Autoload dotenv in Rails.
88
88
  test_files: []