Closed jklmnn closed 6 years ago
what do you think about including a file named config.local.php right after config.php that file would be optional, user-provided and could override everything that was set in config.php of cause config.local.php should not be put into the repo :smiley:
would look like:
include('config.php');
@include('config.local.php');
the advantage would be that the novice user could simply choose to modify the original file and the advanced user could simply create a config.local.php and override what he needs.
Closing this due to inactivity.
We currently have the
config.php
in git. When the user sets it up and then loads a new version, it will be overwritten. We should moveconfig.php
toconfig.php.def
(to keep a definition file) and create a newconfig.php
on install. The same applies to.htaccess
. We also should add those files to.gitignore
to prevent inadvertently pushing of credentials to the repo.