Description of the need
While working with a new Backdrop project, I really needed to be able to quickly set/change the maintenance_mode using override method from command line or the settings.php file. And since the maintenance_mode variable moved to State database table, I could not use the configuration overrides.
Therefore, knowing that implementation of new features to core would take some time, as a quick temporary solution I've pushed very simple State Override module, which literally consists of 13 lines:
<?php
/**
* Implements hook_boot.
*/
function state_override_boot() {
global $config;
if (!empty($config)) {
foreach ($config['state'] as $key => $value) {
state_set($key, $value);
}
}
}
so now I can simply put lines like:
$config['state']['maintenance_mode'] = TRUE;
$config['state']['cron_key'] = 'w5AXKo9UdkoVRp9rT_0gqtdG2h322LGJ_sYuJN6aWpk1';
to settings.php file and it will work just as desired.
However, I believe it would be really useful for automation purposes and convenience of all future Backdrop developers if core supported overriding State variables.
Proposed solution
Let's get this into core if the consensus says so.
Recent comments
@yorkshirepudding thank you for the additional info on improving discoverability and a handy way to keep a list of projects for reuse.
Why not add a Github star?
It is a good point @izmeez and when I was researching repo discoverability I found that GitHub search does prioritise matches with more stars. This is what I was researching for:...
Why not add a Github star?
Do you have a separate development environment and transfer database and config between sites?
Wierd happenings regarding updates...