Open bryanpizzillo opened 1 week ago
There is a 14.0.0-beta2
in the BLT Repo. At this point it does not look like BLT is going to actually release a v14.0.0 version. So it may make sense to fork the repo, and reference our fork in the composer.json instead of acquias. Then we can point at this tag for now.
This would at least allow us to use a cleaner form of BLT with the drupal-recommeneded-settings instead of smushing BLT v13 + coding in ours. (This updates some of the blt commands to add in settings.php for local development as well.)
Forking BLT makes sense from the standpoint of not having the repo disappear out from under us. But we'll (of course) still want to adopt drupal-recommeneded-settings
sooner rather than later.
We should also fork acquia/blt-acsf
as that one is also marked abandoned.
Issue description
BLT handles the Drupal configuration for Acquia environments. This is done through a line at the end of settings.php,
require DRUPAL_ROOT . "/../vendor/acquia/blt/settings/blt.settings.php";
. BLT then added in various settings through plugins and other things. This area is replaced by https://github.com/acquia/drupal-recommended-settings. In addition to "normal" settings, we also need to see how it does, or does not, handle: