Probably most of 4get hosters and selfhosters just clone the repository and modify config.php right away to customize their settings.
If the user modifies config.php, in the next git pull to update the instance, the user will be asked to commit the changes of config.php and then pull the changes from upstream. There is more problems besides just commit the configuration, like conflict issues which are extremely annoying to solve on the terminal and for people that just want a working 4get instance.
IMO this is better.
Probably most of 4get hosters and selfhosters just clone the repository and modify config.php right away to customize their settings.
If the user modifies config.php, in the next `git pull` to update the instance, the user will be asked to commit the changes of config.php and then pull the changes from upstream. There is more problems besides just commit the configuration, like conflict issues which are extremely annoying to solve on the terminal and for people that just want a working 4get instance.
IMO this is better.
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.
Probably most of 4get hosters and selfhosters just clone the repository and modify config.php right away to customize their settings.
If the user modifies config.php, in the next
git pullto update the instance, the user will be asked to commit the changes of config.php and then pull the changes from upstream. There is more problems besides just commit the configuration, like conflict issues which are extremely annoying to solve on the terminal and for people that just want a working 4get instance.IMO this is better.
Also, why not make the https://git.lolcat.ca/lolcat/4get/src/branch/master/data/config.php#L8 a hardcoded value on 4get? Is just the version