dotenv-vault 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 +4 -4
- data/CHANGELOG.md +13 -1
- data/Gemfile.lock +3 -3
- data/README.md +9 -19
- data/lib/dotenv-vault/load.rb +2 -0
- data/lib/dotenv-vault/version.rb +1 -1
- metadata +2 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: e6078bb2cca1c416c7dac1d4b3448dd73407db567df195fe78b974931b36ef35
|
|
4
|
+
data.tar.gz: 7246ef444f59fd1a22cf19ec5b649230105b203a167004eb66fb56aaa7fe5001
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: cb7043c13677592337f463c04e0e91b026e079754b156f49ff47480771f7ed5d45fae900418cbe43363b21970603828bbe8a741100abe41ae32f716f6ff2360f
|
|
7
|
+
data.tar.gz: 06144215e220b404125037dfe2097e2c5c12fc7d03ad7f21d891ce210975576610683baaaf598af7945bee14aaa63d2ba933de87c2a06f2e51f3910193ee3325
|
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.
|
|
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.
|
|
4
|
+
dotenv-vault (0.8.0)
|
|
5
5
|
dotenv
|
|
6
6
|
lockbox
|
|
7
|
-
dotenv-vault-rails (0.
|
|
7
|
+
dotenv-vault-rails (0.8.0)
|
|
8
8
|
dotenv-rails
|
|
9
|
-
dotenv-vault (= 0.
|
|
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
|
|
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
|
-
|
|
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
|
|
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
|
-
|
|
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
|
-
|
|
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
|
data/lib/dotenv-vault/version.rb
CHANGED
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: dotenv-vault
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.
|
|
4
|
+
version: 0.8.0
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- motdotla
|
|
@@ -102,6 +102,7 @@ files:
|
|
|
102
102
|
- dotenv-vault.gemspec
|
|
103
103
|
- lib/dotenv-vault-rails.rb
|
|
104
104
|
- lib/dotenv-vault.rb
|
|
105
|
+
- lib/dotenv-vault/load.rb
|
|
105
106
|
- lib/dotenv-vault/rails-now.rb
|
|
106
107
|
- lib/dotenv-vault/rails.rb
|
|
107
108
|
- lib/dotenv-vault/version.rb
|