Originally created by @rprimet on GitHub (Feb 21, 2017).
Hi,
Should "more-specific" (local) config files (e.g. in SCRIPTDIR or PWD) take precedence over "less specific" ones (e.g. /etc/dehydrated)?
If so, a solution would be to change the search order in load_config.
Originally created by @rprimet on GitHub (Feb 21, 2017).
Hi,
Should "more-specific" (local) config files (e.g. in SCRIPTDIR or PWD) take precedence over "less specific" ones (e.g. /etc/dehydrated)?
If so, a solution would be to change the search order in `load_config`.
(reopening this issue -- using the -f flag may be the best choice, but it seems that giving precedence to local over global files still deserves thinking about?)
@rprimet commented on GitHub (Feb 22, 2017):
(reopening this issue -- using the -f flag may be the best choice, but it seems that giving precedence to local over global files still deserves thinking about?)
I would want the script to explicitly prefer global defaults (if they exist) over whatever local configs may have been accidentally created. If I want to use a non-global config (without removing an existing global config), I can specify that.
@txr13 commented on GitHub (Feb 22, 2017):
I would want the script to explicitly prefer global defaults (if they exist) over whatever local configs may have been accidentally created. If I want to use a non-global config (without removing an existing global config), I can specify that.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @rprimet on GitHub (Feb 21, 2017).
Hi,
Should "more-specific" (local) config files (e.g. in SCRIPTDIR or PWD) take precedence over "less specific" ones (e.g. /etc/dehydrated)?
If so, a solution would be to change the search order in
load_config.@rprimet commented on GitHub (Feb 22, 2017):
(reopening this issue -- using the -f flag may be the best choice, but it seems that giving precedence to local over global files still deserves thinking about?)
@txr13 commented on GitHub (Feb 22, 2017):
I would want the script to explicitly prefer global defaults (if they exist) over whatever local configs may have been accidentally created. If I want to use a non-global config (without removing an existing global config), I can specify that.
@rprimet commented on GitHub (Feb 22, 2017):
OK, closing it for good then :)