Feature proposal: have local config to avoid loosing it on update - #185
Open
Jeremie-Kiwik wants to merge 1 commit into
Open
Feature proposal: have local config to avoid loosing it on update#185Jeremie-Kiwik wants to merge 1 commit into
Jeremie-Kiwik wants to merge 1 commit into
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Here is a feature proposal to address a common problem: when we extract a ZIP file of a newer version of the project onto our current source files, any locally defined configurations are lost because config.php is overwritten.
I propose addressing this issue by introducing the option to have a local configuration file, which would be read if present, instead of the standard file. This approach is similar to the way configuration files are handled in
/etc/xx/conf.don Linux systems.