Allow to overwrite the auth secret key with env var #480
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
You can overwrite the `auth::secret_key` in the config file: ```toml [auth] email_on_signup = "Optional" min_password_length = 6 max_password_length = 64 secret_key = "MaxVerstappenWC2021" ``` With an env var: `TORRUST_INDEX_AUTH_SECRET_KEY`. That will make it easier to inject secrets when you use docker without modifying the configuration file: `config.toml`.
josecelano
added
Continuous Integration
|
ACK 9d8cf7b |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
You can overwrite the
auth::secret_keyin the config file:With an env var:
TORRUST_INDEX_AUTH_SECRET_KEY.That will make it easier to inject secrets when you use docker without modifying the configuration file:
config.toml.