Load config file from OXIDIZED_HOME env var location. #2479
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
|
This branch is on top of my 'rubocop-fixes' branch, hence the extra commits. |
Reduces Cyclomatic and Percieved complexity Signed-off-by: Mike Beattie <[email protected]>
Signed-off-by: Mike Beattie <[email protected]>
mjbnz
force-pushed
the
config-from-home-envvar
branch
from
a6c1c12 to
c22e4e0
Compare
ghost
merged commit
This pull request was closed.
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.
Pre-Request Checklist
rubocop --auto-correct)rake test)Description
Using
$OXIDIZED_HOMEdoesn't change the load location of the config file, this PR adds that functionality by setting theusrdiroption to theasetusmodule to the oxidized config root value.