bridgetown_credentials 1.2.0 → 1.3.1

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.
Files changed (5) hide show
  1. checksums.yaml +4 -4
  2. data/CHANGELOG.md +10 -0
  3. data/README.md +15 -0
  4. data/lib/bridgetown_credentials/version.rb +1 -1
  5. metadata +6 -5
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: aa69828861ac1149851e406f310b0caaefcf9747b2dced644339ffde8c3d5f77
4
- data.tar.gz: 6d3f5feb61337bc0c42a662bb3c5447d61fd15d8dd2ec34aea9bd64fb151dbd8
3
+ metadata.gz: 9a9528c4249f25673cc3bb309c97e61d59fe0ce9b8b98be1645b7dceb59213d8
4
+ data.tar.gz: ae0e7340b5f3b56cd38f6afae79bec3a750c22fb9ed1e04755eec72f29e3e63d
5
5
  SHA512:
6
- metadata.gz: 135e0e7b78674f948162a3636e2337dd1ec4acef1093318b9674d99b8e236fd87573616c0755ace133a5120dd411e75e6eecb6da3ebd84a8a5f0dfb4499be0e3
7
- data.tar.gz: 17c34f2c532ad43358f10b2144ed6d5059a4c1c4708d298aaf99a87f9d9d82d2d42dfa4c6eb9b60a091606c2befb1dc0f9a82eda4596e34c27668a89bf3e7073
6
+ metadata.gz: 9925317457ee123addb89de3a404503f00dab7694a6d10896b8831a7e75b51713a248c088f52b0b55ff49c60793182b2ef172120445a8c0aafae65b2032f3d3a
7
+ data.tar.gz: 2460b4bbb5b4b08b294bca8c50d3cbeab9f3191fb1a4ac4a1d3c3dd14cc943ea19b76f17292e4f47fe3eefa2475e05f07bbe01251b4e06b73826dd19597df22a
data/CHANGELOG.md CHANGED
@@ -2,6 +2,16 @@
2
2
 
3
3
  Nothing so far
4
4
 
5
+ ## 1.3.1
6
+
7
+ ### Improvements
8
+ * Enforce MFA for future gem releases
9
+
10
+ ## 1.3.0
11
+
12
+ ### Additions
13
+ * Allow keys to be read from file e.g. `CREDENTIALS_KEY_FILE`
14
+
5
15
  ## 1.2.0
6
16
 
7
17
  ### Changes
data/README.md CHANGED
@@ -104,6 +104,19 @@ export DEVELOPMENT_CREDENTIALS_KEY="4c87...af93"
104
104
  export PRODUCTION_CREDENTIALS_KEY="92bb...820f"
105
105
  ```
106
106
 
107
+ Alternatively, you can omit the first part of the variable name. Such a key will be used for any app environment, but a more specific key will always take precedence. This is particularly useful when working with containerized setups:
108
+
109
+ ```sh
110
+ export CREDENTIALS_KEY="4c87...af93"
111
+ ```
112
+
113
+ You can also read keys from files which is the recommended way when using [secrets in Docker Compose](https://docs.docker.com/compose/how-tos/use-secrets/). Just append `_FILE` to the corresponding environment variable name and set it to the path from which the secret can be read, for example:
114
+
115
+ ```db
116
+ export DEVELOPMENT_CREDENTIALS_KEY_FILE=/run/secrets/sandbox_credentials_key
117
+ export CREDENTIALS_KEY_FILE=/run/secrets/credentials_key
118
+ ```
119
+
107
120
  ### Edit
108
121
 
109
122
  The command is the same as the first time:
@@ -131,3 +144,5 @@ Bridgetown.credentials.google.maps.api_key # => "goomXkey"
131
144
  ## Development
132
145
 
133
146
  You're welcome to [submit issues](https://github.com/svoop/bridgetown_credentials/issues) and contribute code by [forking the project and submitting pull requests](https://docs.github.com/en/get-started/quickstart/fork-a-repo).
147
+
148
+ By the way: The underscore in the gem name "bridgetown_credentials" is no accident. While the common gem naming convention rather suggests a dash, [Bridgetown chose to prefer underscores for its plugins](https://www.bridgetownrb.com/docs/plugins#creating-a-gem).
data/lib/bridgetown_credentials/version.rb CHANGED
@@ -1,5 +1,5 @@
1
1
  # frozen_string_literal: true
2
2
 
3
3
  module BridgetownCredentials
4
- VERSION = "1.2.0"
4
+ VERSION = "1.3.1"
5
5
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: bridgetown_credentials
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.2.0
4
+ version: 1.3.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Sven Schwyn
@@ -29,14 +29,14 @@ dependencies:
29
29
  requirements:
30
30
  - - ">="
31
31
  - !ruby/object:Gem::Version
32
- version: 0.2.1
32
+ version: 0.6.0
33
33
  type: :runtime
34
34
  prerelease: false
35
35
  version_requirements: !ruby/object:Gem::Requirement
36
36
  requirements:
37
37
  - - ">="
38
38
  - !ruby/object:Gem::Version
39
- version: 0.2.1
39
+ version: 0.6.0
40
40
  - !ruby/object:Gem::Dependency
41
41
  name: debug
42
42
  requirement: !ruby/object:Gem::Requirement
@@ -168,8 +168,9 @@ metadata:
168
168
  homepage_uri: https://github.com/svoop/bridgetown_credentials
169
169
  changelog_uri: https://github.com/svoop/bridgetown_credentials/blob/main/CHANGELOG.md
170
170
  source_code_uri: https://github.com/svoop/bridgetown_credentials
171
- documentation_uri: https://www.rubydoc.info/gems/bridgetown_credentials
171
+ 'documentation_uri ': https://www.rubydoc.info/gems/bridgetown_credentials
172
172
  bug_tracker_uri: https://github.com/svoop/bridgetown_credentials/issues
173
+ rubygems_mfa_required: 'true'
173
174
  post_install_message: "⚠️ Breaking change: bridgetown_credentials >= 1.0.0 no longer
174
175
  depends on ActiveSupport. Please read the update section in the README for how to
175
176
  migrate your Bridgetown site. Don't worry, it's a piece of cake!"
@@ -194,7 +195,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
194
195
  - !ruby/object:Gem::Version
195
196
  version: '0'
196
197
  requirements: []
197
- rubygems_version: 4.0.3
198
+ rubygems_version: 4.0.6
198
199
  specification_version: 4
199
200
  summary: Rails-like encrypted credentials for Bridgetown
200
201
  test_files: