dotenv-vault-rails 0.7.1 → 0.8.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: e91991151b13e9afd810b5e8d8bdc14f8af6019e17f6ec103a37bc1bf8a2d4e3
4
- data.tar.gz: 70d8a1939630149570a0873f02af6dff4c796bfc2ff5860693d305ada37fd480
3
+ metadata.gz: 81836f8e99d481c8ae8dc9ab69c6be7c9bc2275d86ab29025db14ad9a31c4a67
4
+ data.tar.gz: e9e4296b3dd37d4b27f9d2ebc0d3bb9965c1aeb2e33377aaad02ad76527b6a4c
5
5
  SHA512:
6
- metadata.gz: 0f6b4372e769083a970bca589926fc17831c2dbae97ddd49cd0bbce7442242fdea69fa06407dd6d219c1c9c2948b861499f29dade4a16517f529cb03ddf3d14c
7
- data.tar.gz: 2ddcf5cdf739284fc528803f1747536383c742689b48d65d599461df2c89c9063e182821f2630fb9f5ad40ff09ff68eff32f284e66187d1f693d88c7b059d60b
6
+ metadata.gz: bf1c763c3304ae0a6e8275298187c6a836578e6e6fe6941d4f1fb7276d158c215e4a9347b28e4ae012b02a52da710dc289f04bcf7c631b6ad9dd3281dde24caf
7
+ data.tar.gz: 03d12b9d8dfe69f723394076b20cae13a4fc1d7daa550f3b8322bc6ff7ca71735c5368600adf62bdbdea27eeafcad3f048541b135ebefec4a27c6901e64118cb
data/CHANGELOG.md CHANGED
@@ -2,7 +2,19 @@
2
2
 
3
3
  All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
4
4
 
5
- ## [Unreleased](https://github.com/dotenv-org/dotenv-vault-ruby/compare/v0.7.0...master)
5
+ ## [Unreleased](https://github.com/dotenv-org/dotenv-vault-ruby/compare/v0.8.0...master)
6
+
7
+ ## 0.8.0
8
+
9
+ ### Added
10
+
11
+ - Add `dotenv-vault/load`
12
+
13
+ ## 0.7.1
14
+
15
+ ### Added
16
+
17
+ - Added README
6
18
 
7
19
  ## 0.7.0 and prior
8
20
 
data/Gemfile.lock CHANGED
@@ -1,12 +1,12 @@
1
1
  PATH
2
2
  remote: .
3
3
  specs:
4
- dotenv-vault (0.7.1)
4
+ dotenv-vault (0.8.0)
5
5
  dotenv
6
6
  lockbox
7
- dotenv-vault-rails (0.7.1)
7
+ dotenv-vault-rails (0.8.0)
8
8
  dotenv-rails
9
- dotenv-vault (= 0.7.1)
9
+ dotenv-vault (= 0.8.0)
10
10
 
11
11
  GEM
12
12
  remote: https://rubygems.org/
data/README.md CHANGED
@@ -76,23 +76,9 @@ $ npx dotenv-vault open production
76
76
 
77
77
  It will open up an interface to manage your production environment variables.
78
78
 
79
- ..or if you prefer to manage them in your text editor, run the command:
80
-
81
- ```shell
82
- $ npx dotenv-vault pull production
83
- ```
84
-
85
- Edit the `.env.production` file and push your changes:
86
-
87
- ```shell
88
- $ npx dotenv-vault push production
89
- ```
90
-
91
- Neato.
92
-
93
79
  ## Deploy Anywhere
94
80
 
95
- Build your encrypted `.env.vault`. Run the command:
81
+ Build your encrypted `.env.vault`:
96
82
 
97
83
  ```shell
98
84
  $ npx dotenv-vault build
@@ -121,18 +107,22 @@ All set! When your app boots, it will recognize a `DOTENV_KEY` is set, decrypt t
121
107
 
122
108
  ## FAQ
123
109
 
124
- ### What happens if DOTENV_KEY is not set?
110
+ #### What happens if `DOTENV_KEY` is not set?
125
111
 
126
- Dotenv Vault gracefully falls back to [dotenv](https://github.com/bkeepers/dotenv) when `DOTENV_KEY` is not set. This is useful for development.
112
+ Dotenv Vault gracefully falls back to [dotenv](https://github.com/bkeepers/dotenv) when `DOTENV_KEY` is not set. This is the default for development so that you can focus on editing your `.env` file and save the `build` command until you are ready to deploy those environment variables changes.
127
113
 
128
- ### Should I commit my `.env` file?
114
+ #### Should I commit my `.env` file?
129
115
 
130
116
  No. We **strongly** recommend against committing your `.env` file to version control. It should only include environment-specific values such as database passwords or API keys. Your production database should have a different password than your development database.
131
117
 
132
- ### Should I commit my `.env.vault` file?
118
+ #### Should I commit my `.env.vault` file?
133
119
 
134
120
  Yes. It is safe and recommended to do so. It contains your vault identifier at the vault provider (in this case [dotenv.org](https://dotenv.org)) and contains your encrypted values.
135
121
 
122
+ #### Can I share the `DOTENV_KEY`?
123
+
124
+ No. It is the key that unlocks your encrypted environment variables. Be very careful who you share this key with. Do not let it leak.
125
+
136
126
  ## Contributing
137
127
 
138
128
  1. Fork it
@@ -0,0 +1,2 @@
1
+ require "dotenv-vault"
2
+ DotenvVault.load
@@ -1,3 +1,3 @@
1
1
  module DotenvVault
2
- VERSION = "0.7.1"
2
+ VERSION = "0.8.0"
3
3
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: dotenv-vault-rails
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.7.1
4
+ version: 0.8.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - motdotla
@@ -30,14 +30,14 @@ dependencies:
30
30
  requirements:
31
31
  - - '='
32
32
  - !ruby/object:Gem::Version
33
- version: 0.7.1
33
+ version: 0.8.0
34
34
  type: :runtime
35
35
  prerelease: false
36
36
  version_requirements: !ruby/object:Gem::Requirement
37
37
  requirements:
38
38
  - - '='
39
39
  - !ruby/object:Gem::Version
40
- version: 0.7.1
40
+ version: 0.8.0
41
41
  - !ruby/object:Gem::Dependency
42
42
  name: spring
43
43
  requirement: !ruby/object:Gem::Requirement
@@ -88,6 +88,7 @@ files:
88
88
  - dotenv-vault.gemspec
89
89
  - lib/dotenv-vault-rails.rb
90
90
  - lib/dotenv-vault.rb
91
+ - lib/dotenv-vault/load.rb
91
92
  - lib/dotenv-vault/rails-now.rb
92
93
  - lib/dotenv-vault/rails.rb
93
94
  - lib/dotenv-vault/version.rb