I maintain a pretty hefty config.php file - one that contains many settings for things throughout the system. Storing all of these values in config.php makes deploying and moving things very, very easy, but I keep running into an issue and there has to be a good solution.
Whenever I log into an EE CP and start editing settings in the ‘admin’ section, they normally overwrite my custom config.php file (since we’re told to set this file’s permissions to 666). To get around this, I set permissions to 644 so that EE can’t overwrite this file. This would solve the problem, except that trying to save settings in the CP triggers errors (since the CP expects to overwrite the file but can’t). This is fine for me, but wholly confusing for clients.
How can I use a custom config.php file while also allowing myself and my clients to edit settings in the CP? I’m not expected a cut and dry answer, but there’s got to be a better way of handling this. Any thoughts?