Support custom config file locations via environment variables #1987
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
NorthIsUp
changed the title
NorthIsUp
force-pushed
the
adam/1-support_xdg_config_file_standard
branch
from
274b7e7
to
269e66a
Compare
|
pretty plz. |
|
Seems like a pretty straight forward & sensible PR for a long-requested feature. @lra any thoughts on this PR? Thanks! 🙏 |
|
Agreed, this should be implemented. Those concerned with their config settings are often concerned with organizing where those config files are stored. |
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.
This adds support for a custom config file location via the new
$MACKUP_CONFIGvar or by checking for$XDG_CONFIG_HOME.It searches for config files in the following order:
~/.mackup.cfg$MACKUP_CONFIG$XDG_CONFIG_HOME/mackup/mackup.cfg~/.config/mackup/mackup.cfgif none of these exist
~/.mackup.cfgis created and used