You are here
Drupal 8 API tutorials
Want to learn about the Drupal 8 APIs, with worked examples? Follow my series of tutorials, covering routing, caching, entities, config and much more!
Want to hire me?
Recent blogposts
-
Altering the length of a Drupal 8 text field that contains data
Friday, July 21, 2017 - 11:31 -
A menagerie of testing: behavioural, unit, system, smoke, regression, oh my!
Friday, June 2, 2017 - 10:11 -
Including Javascript in Behat tests, all inside a headless, virtual machine
Tuesday, May 30, 2017 - 16:51
About me
I'm J-P Stacey, and I'm a freelance technical developer and software architect, working with Drupal, Javascript, Symfony, PHP and devops, with experience in project and process management and an emphasis on usability.
I live in the UK; my website is self-hosted on bigv.io; my email is hosted by Google, and that's also what I use to share files. (More info|What is this?)
As far as I'm aware, the fact
As far as I'm aware, the fact that a composer package is from a git repository doesn't preclude adding a composer/installers type, so you should still be able to do that. As I say, I'm pretty certain I wrote drush m2c to support this, so if you try running your makefile through that then it should do all that for you. If it doesn't then do raise an issue on its github project.
Also, if you use Drush Instance to run all this for you, it builds sites/all/modules and sites/default for you post-make/composer, so you don't need to embed further post-update-cmd in composer.json. It will also rebuild your codebase (its equivalent of an update is a full rebuild, but mostly from caches), preserving your uploads directory, sites/default and any other custom file locations.