-
Notifications
You must be signed in to change notification settings - Fork 394
BLT errors on Windows 10 #1078
Comments
BLT makes the assumption that you are using features to manage your configuration. See http://blt.readthedocs.io/en/8.x/readme/features-workflow/ It appears that you are instead using core CM to manage your entire site's configuration. This is not compatible with the I think your options are:
What we could do in BLT itself is add a new configuration option that would allow you to optionally use Core CM. Please open a feature request if you're interested in that route. |
… partial flag to be configurable.
…uration directory and partial flag to be configurable.
Thank you @grasmash, with Option 2 I was able to run I then pulled from our upstream develop branch to get all the changes (since the last time I did that) and then tried
Where do I go from here? |
@meancode is |
I have downloaded the drush aliases, I have them installed in Windows, and in Umbuntu Bash, But how do I copy them over inside the Vagrant guest VM? Thanks! |
@grasmash Nevermind on getting the files into the Vagrant VM, I have added my Acquia Cloud drush aliases, as well as my SSH key. I am, however, still getting errors on
|
I was asked to post an issue here by Aquia Support.
My system information:
Output of
blt doctor
:When I run this command:
I get the following output:
And I expected this to happen:
I expect to see all the changes that the other people in our team have committed to Git, up and running locally in Drupal.
Even when I initially run
blt local:setup
that was not without errors. Output fromblt local:setup
is below:I can sign into Drupal at this point, but is a vanilla install. When I run
blt local:refresh
I no longer have a Drupal installed asblt doctor
clearly shows in red.Worth noting I only got this far because of Jeff Geerling's screencast.
The text was updated successfully, but these errors were encountered: