home-dotenv 0.0.1 → 0.0.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- metadata +3 -45
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: cf4a8e733ad1ad88b9a107637aad82d9555a179b
|
|
4
|
+
data.tar.gz: 34550753dad7a22ae779dd1bb93a109bae7623a7
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 78bf4e5447b217d0793932a8122303292de4fdc32bc3d259118540a4ce7422042a7f018122740db6f7af2f03fe1a7d622e783da7f4db42c78a851d003b045c87
|
|
7
|
+
data.tar.gz: 04d2ce7b9cbd597519ce4ec106b0d1772ddf5f4f7aa6e6653fef780f63afb0138223f84f9f4bd987cb1a4cb0529dd0b7aff8d47ab5413baffd8c4a708bb1617a
|
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: home-dotenv
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.0.
|
|
4
|
+
version: 0.0.2
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Dorian Marié
|
|
@@ -10,49 +10,7 @@ bindir: bin
|
|
|
10
10
|
cert_chain: []
|
|
11
11
|
date: 2017-02-25 00:00:00.000000000 Z
|
|
12
12
|
dependencies: []
|
|
13
|
-
description:
|
|
14
|
-
# `home-dotenv`
|
|
15
|
-
|
|
16
|
-
## Instalation
|
|
17
|
-
|
|
18
|
-
``ruby
|
|
19
|
-
gem install home-dotenv
|
|
20
|
-
|
|
21
|
-
# or in a Gemfile
|
|
22
|
-
gem 'home-dotenv'
|
|
23
|
-
```
|
|
24
|
-
|
|
25
|
-
## Explanation
|
|
26
|
-
|
|
27
|
-
So, you have scripts run on your system and you have config variables for those
|
|
28
|
-
scripts (keys, usernames, passwords, hostnames, etc).
|
|
29
|
-
|
|
30
|
-
A unified way to access those globals would be nice instead of hard-coding them
|
|
31
|
-
or passing them as parameters.
|
|
32
|
-
|
|
33
|
-
So, now you can put all your variables in ~/.env like so:
|
|
34
|
-
|
|
35
|
-
```
|
|
36
|
-
SUPER_SECRET_PASSWORD=i-definitely-don-t-want-people-to-see-this
|
|
37
|
-
AWS_KEY=abcdefgh
|
|
38
|
-
SECRET_HOST=https://private.secret.com
|
|
39
|
-
```
|
|
40
|
-
|
|
41
|
-
Then, in your scripts:
|
|
42
|
-
|
|
43
|
-
```
|
|
44
|
-
require 'home-dotenv'
|
|
45
|
-
HOME_ENV = HomeDotenv.parse
|
|
46
|
-
|
|
47
|
-
require 'open-uri'
|
|
48
|
-
open(HOME_HOME[:SECRET_HOST]).read
|
|
49
|
-
```
|
|
50
|
-
|
|
51
|
-
Parsing rules:
|
|
52
|
-
|
|
53
|
-
- if the line is empty or starts by "#" (comment), ignore
|
|
54
|
-
- otherwise, string before the first "=" is key, after that it's the value
|
|
55
|
-
- result is a hash indexed by symbol, e.g. HOME_ENV[:AWS_KEY]
|
|
13
|
+
description: Use ~/.env as your source of keys/secrets/etc for your scripts
|
|
56
14
|
email: dorian@doma.io
|
|
57
15
|
executables: []
|
|
58
16
|
extensions: []
|
|
@@ -82,5 +40,5 @@ rubyforge_project:
|
|
|
82
40
|
rubygems_version: 2.6.8
|
|
83
41
|
signing_key:
|
|
84
42
|
specification_version: 4
|
|
85
|
-
summary:
|
|
43
|
+
summary: Parse ~/.env file for your scripts
|
|
86
44
|
test_files: []
|