We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Depends on:
auth::secret_key
auth::user_claim_token_pepper
After finishing the last configuration changes in the Index, those last changes must be applied here.
metadata
[metadata] app = "torrust-index" purpose = "configuration" schema_version = "2.0.0"
secret_key option was renamed to user_claim_token_pepper.
secret_key
user_claim_token_pepper
And some options were made mandatory:
[metadata] schema_version = "2.0.0" [logging] threshold = "info"
From TORRUST_INDEX_CONFIG_OVERRIDE_AUTH__SECRET_KEY to TORRUST_INDEX_CONFIG_OVERRIDE_AUTH__USER_CLAIM_TOKEN_PEPPER
TORRUST_INDEX_CONFIG_OVERRIDE_AUTH__SECRET_KEY
TORRUST_INDEX_CONFIG_OVERRIDE_AUTH__USER_CLAIM_TOKEN_PEPPER
The text was updated successfully, but these errors were encountered:
fix: [torrust#591] update index configuration
847500a
Merge #594: Update index configuration
c4aaa7a
847500a fix: [#591] update index configuration (Jose Celano) Pull request description: Update index configuration. ACKs for top commit: josecelano: ACK 847500a Tree-SHA512: 598e23b3220d5193e917aa87eb6b6960dce04457c787e0947646b99d131aa82988858a0789154c56171aba1e49ef7a48833f76d342e878c4b382c51360730a1e
josecelano
Successfully merging a pull request may close this issue.
Depends on:
auth::secret_key
toauth::user_claim_token_pepper
torrust-index#653After finishing the last configuration changes in the Index, those last changes must be applied here.
metadata
section was changed:secret_key
option was renamed touser_claim_token_pepper
.And some options were made mandatory:
From
TORRUST_INDEX_CONFIG_OVERRIDE_AUTH__SECRET_KEY
toTORRUST_INDEX_CONFIG_OVERRIDE_AUTH__USER_CLAIM_TOKEN_PEPPER
The text was updated successfully, but these errors were encountered: