Description
Is your feature request related to a problem? Please describe.
I have a couple of perlite sites, configured by editing helper.php
When updating perlite, I have to make a copy of helper.php, then re-add my configuration.
Describe the solution you'd like
I'd like a separate file named something like 'config.php' that can hold any custom configuration. Ideally, it wouldn't be included in releases, so that I could update perlite without overwriting my configuration.
Describe alternatives you've considered
It might be simpler/better to have the default configuration in one file (eg config.php) and any overriding local configuration in another file (eg config_local.php)
Additional context
This is a setup I've seen used to good effect in other server software such as Kanboard and Dokuwiki.