Backdrop core already supports reading configuration from a settings.local.php file (see https://github.com/backdrop/backdrop/blob/1.x/settings.php#L458), although there's no such file shipped with core OOTB - it needs to be created manually.
Drush currently supports this:
drush si standard --db-url=mysql://root:backdrop@localhost/backdrop --site-name="My test site"
Additionally, I would like to be able to do something like this:
drush si standard --db-url=mysql://root:backdrop@localhost/backdrop --site-name="My test site" --settings-path=settings.local.php
This would allow the settings.php file in my local to remain unchanged, so that I do not have to manually exclude it when doing git add (settings.local.php is automatically excluded OOTB: https://github.com/backdrop/backdrop/blob/1.x/.gitignore#L5).
As it is now, I have to:
- run
drush si -> things get saved into settings.php
- manually create a
settings.local.php file
- manually copy things from
settings.php to settings.local.php
Allowing drush si to accept a parameter to specify the settings file would save me the 2 manual steps from the process above.
Backdrop core already supports reading configuration from a
settings.local.phpfile (see https://github.com/backdrop/backdrop/blob/1.x/settings.php#L458), although there's no such file shipped with core OOTB - it needs to be created manually.Drush currently supports this:
Additionally, I would like to be able to do something like this:
This would allow the
settings.phpfile in my local to remain unchanged, so that I do not have to manually exclude it when doinggit add(settings.local.phpis automatically excluded OOTB: https://github.com/backdrop/backdrop/blob/1.x/.gitignore#L5).As it is now, I have to:
drush si-> things get saved intosettings.phpsettings.local.phpfilesettings.phptosettings.local.phpAllowing
drush sito accept a parameter to specify the settings file would save me the 2 manual steps from the process above.