config file order #198

Closed
opened 2025-12-29 01:18:43 +01:00 by adam · 3 comments
Owner

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`.
adam closed this issue 2025-12-29 01:18:43 +01:00
Author
Owner

@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?)

@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?)
Author
Owner

@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.

@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.
Author
Owner

@rprimet commented on GitHub (Feb 22, 2017):

OK, closing it for good then :)

@rprimet commented on GitHub (Feb 22, 2017): OK, closing it for good then :)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#198