Conversation
This commit introduces support for managing sensitive environment variables using secret files in the eXo Platform Docker image. - Environment variables prefixed with EXO_SEC_ and suffixed with _FILE are read from the specified file paths. - The file contents are exported as standard environment variables for use by the application. - Enables secure handling of passwords, API keys, and private keys without hardcoding them in Docker commands or Compose files. Example usage: EXO_SEC_DB_PASSWORD_FILE=/run/secrets/exo_db_password EXO_SEC_MAIL_SMTP_PASSWORD_FILE=/run/secrets/exo_mail_smtp_password
Contributor
|
if both envs (with SEC and without) are put, is there a priority? Shall We add test on that? |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This commit introduces support for managing sensitive environment variables using secret files in the eXo Platform Docker image.
Example usage: