- 🇦🇺Australia darvanen Sydney, Australia
As this ticket is for 7.x and Drupal 7 is now out of support I am closing this ticket as outdated.
I think the practice of overriding $config in the settings file is well-known by now.
While the module is already a great improvement for hardening vanilla Drupal's, I would love to see a bit more CI "friendliness". What would you think about settings.php definitions (just like many other modules do, e. g. memcached or varnish or whatever). I. e., loading certain rules from code and not (only) from DB. This makes it easier to maintain branches and stuff, and also setting up different IP ranges depending on the environment, e.g. with the sitematcher module → I created for just this.
I would also take the effort of providing a patch for this, given that you support my initiative :)
(You know the story, prod DBs are prone to be "quickly" cloned for a local dev setup, and unless you maintain some SQL script magic for such cases, you quickly have avoidable issues.)
Looking forward to your opinion, here or also by PM if you prefer :)
Closed: outdated
3.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
As this ticket is for 7.x and Drupal 7 is now out of support I am closing this ticket as outdated.
I think the practice of overriding $config in the settings file is well-known by now.