Closed tabroughton closed 5 years ago
I'm updating from 1) to 2) as both are as flaky as each other but 2) is a bit neater.
I will request a PR upstream on the backdrop drush project
Boom - it's been accepted :)
will need to review dependency management etc so I'll raise an issue for that #18
In order to run civicrm-install we backdrop needs to know about the command but the backdrop drush scripts will only detect commands from modules that are enabled.
Enabling civicrm before installing causes catastrophic errors. Not good.
We have had a hack in place to keep a local copy of backdrop.drush.inc which whitelists drush commands backdrop can run. We entered into the list the civicrm-install command, then we kept this local to the backdrop-civicrm-docker project, copying it to the correct place when deploying the containers.
This will cause issues as the file isn't updated when the parent project (backdrop-contrib/drush) updates. We need alternative solution.
Options: