Allow environment variables in server configs#101
Merged
Conversation
Contributor
|
Looks like user ns still references recently removed config methods causing the repl not to start for me |
Contributor
Author
I've fixed this now. |
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
3 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 patch removes the majority of the configuration processing and parsing code in favor of that added to the db library in fluree/db#943. The only configuration parsing and initialization code left here is that which is specific to fluree/server. This patch also makes use of the environment variable aware configuration parsing code added in fluree/db#943 so that users can specify that certain values should be loaded from environment variables.