ENH: Adds the abillity to pass a path to an alternate config file to run badger #121
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
…t is not the default one stored in the user folder
… which holds the config settings in badger
roussel-ryan
approved these changes
Nov 6, 2024
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.
Description
Adds a argument flag -cf or --config_filepath which can be used when launching badger to have it read and write to a config file that is not the default one in the user folder.
For example if badger is launched with: badger -g -cf "path/to/config/example_config.yaml" then the setting from the example_config.yaml are loading in to badger and any changes made are saved back to the example_config.yaml. if badger is then launched with just badger -g it will instead load the config settings from the default config file.
This only works for the GUI version of badger.