Wallogit.com
2017 © Pedro Peláez
This library provides tools for an opinionated composer workflow with Drupal., (*1)
When invoked, it creates a Drupal root that can respond to requests routed to it from a web server. This allows you to develop at the module and/or project level and treat Drupal itself as a dependency., (*2)
Use composer., (*3)
The algorithm is something like this:, (*4)
drupal/drupal out of vendor and into the given drupal path (default:
./www)./modules directory into sites/all/modules
./themes directory into sites/all/themes
sites/all/modules according to the basename of the *.info filecnf/settings.php into sites/default
vendor into sites/default
cnf/files into sites/default
You have the choice of using a small commandline application or a script handler., (*5)
vendor/bin/drupal_tangle -h Usage: drupal:tangle [project] [drupal] Arguments: project path to project to tangle drupal path to drupal in which to tangle (default: "www")
You can automate the use of the tangler in response to composer events like so:, (*6)
{
...
"scripts": {
"post-install-cmd": [
"Drupal\\Tangler\\ScriptHandler::postUpdate",
],
"post-update-cmd": [
"Drupal\\Tangler\\ScriptHandler::postUpdate"
]
},
...
}
Note that you can just trigger the executable with these events, in which case
the values for the different *-cmd events above would be like this:, (*7)
[ "vendor/bin/drupal_tangle" ]
settings.php
sites/all/libraries directory (not
because this is ever a good idea, but because some projects require it)