Closed ctrladel closed 7 years ago
@ctrladel - Thanks for filing the issue! I'll try to take a look in a little bit after I wrap up a couple other things here at the DrupalCon sprints.
Changing the paths in example.drupal.composer.json to use web instead of docroot fixed my issue
"extra": {
"installer-paths": {
"web/core": ["type:drupal-core"],
"web/modules/contrib/{$name}": ["type:drupal-module"],
"web/profiles/contrib/{$name}": ["type:drupal-profile"],
"web/themes/contrib/{$name}": ["type:drupal-theme"],
"drush/contrib/{$name}": ["type:drupal-drush"]
}
},
Yes the documentation does mention changing drupal_core_path to use docroot instead of web. It might be more simple to change the example.drupal.composer.json as above and update documentation.
I'd agree with changing the json file since I was able to get to that error by just reading what was in the config file. Having that second step hidden in the docs is not very obvious.
@joestewart / @ctrladel - Thanks for confirming! I'll try to get to this today, or if someone else wants to take a stab at a PR before me, please feel free to do so. I'm working on the Docker issue currently.
Issue Type
Your Environment
Your OS
Full console output
https://gist.github.com/ctrladel/3efde4e2f676fc8251257f68335f959e
Summary
Was trying to provision a new vm using the example.drupal.composer.json and ran into the below error. Looks like the installer paths in example.drupal.composer.json don't match up with the path provided in the default config file for drupal_composer_install_dir.
Error from the gist: