Slides of my talk at Drupalcamp Madrid 2017, about composer, and how to integrate it in a Drupal 8 development workflow.

1. EXPLORING COMPOSER IN DRUPAL 8
WITH DRUPAL-PROJECT
Salvador Molina
#DrupalCampEs
www.adevfromtheplains.com
Original talk by @isholgueras

2. Greetings!
I am Salva Molina
● Drupal Developer @ Bluespark.
● Slv_ /”self”/ in drupal.org.
● @Salva_bg on Twitter.
● https://github.com/salvamomo/.
● Rants, cries and nonsense at http://adevfromtheplains.com.

3. Let’s talk about
Composer
1. Composer basics.
1. Drupal-project.
1. Wrapping up.

4. Composer basics
- What is it?
- Main Commands

5. What is Composer?
● Dependency Manager.
● Not a Package Manager.
● Inspired by node’s npm and Ruby’s bundler.

6. composer.json
{
"name": "my-vendor/my-project",
"require": {
"monolog/monolog": "1.0.*",
"consolidation/robo": "^1.0"
},
"require-dev": {
"phpunit/phpunit": "~4.8"
},
"minimum-stability": "dev",
"prefer-stable": true,
}

7. composer.lock
{
"name": "consolidation/robo",
"version": "1.0.5",
"source": {
"type": "git",
"url": "https://github.com/consolidation/Robo.git",
"reference": "1f1d92807f72901e049e9df048b412c3bc3652c9"
},
"dist": {
"type": "zip",
"url": "https://api.github.com/repos/consolidation/Robo/zipball/d064",
"Reference": "1f1d92807f72901e049e9df048b412c3bc3652c9",
},

8. Installing Composer
● Global is better
curl -sS https://getcomposer.org/installer | sudo php -- --
install-dir=/usr/local/bin --filename=composer

9. Main commands
▷ composer init

10. Main commands
▷ composer init
▷ composer install
1
2
3

11. Main commands
▷ composer init
▷ composer install
▷ composer update
1
2
3

12. Main commands
▷ composer init
▷ composer install
▷ composer update
▷ composer require

13. Vendor and autoload.php
Autoload.php
Has all registered classes and namespaces.
/vendor
Directory where libraries are stored.
<?php
// File: ./app.php
require_once “./vendor/autoload.php”

14. What is Autoload.php for?
DependenciesAutoload.phpCustom code

16. Drupal-project
- What is Drupal-project?
- Daily management
- Under the hood

17. Drupal Composer
Working group for making Drupal work with Composer:
http://drupal-composer.org
Composer template for Drupal Projects:
https://github.com/drupal-composer/drupal-project
Drupal Project

18. What does the template do?
● Installs Drupal in the web directory.
● Alters Drupal’s default autoloader to point at the one
generated by composer, in the project root.

19. What does the template do?
Modules (packages of type drupal-module) will be placed in
web/modules/contrib/
Themes (packages of type drupal-theme) will be placed in
web/themes/contrib/
Profiles (packages of type drupal-profile) will be placed in
web/profiles/contrib/

20. What does the template do?
Creates default writable versions of settings.php and
services.yml.
Creates sites/default/files-directory.
Latest version of drush is installed locally for use at
vendor/bin/drush.
Latest version of DrupalConsole is installed locally for use at
vendor/bin/drupal.

21. In one command
composer create-project
drupal-composer/drupal-project:8.x-dev
my-project-dir
--stability dev
--no-interaction
my-project-dir
├── .gitignore
├── composer.json
├── composer.lock
├── config
├── drush
├── LICENSE
├── phpunit.xml.dist
├── README.md
├── scripts
├── vendor
└── web

22. Daily management
The bread and butter of Drupal with drupal-project

23. Starting from scratch
> ~ $ git clone https://git/repo.git
> ~ $ cd repo
> ~/repo $ composer install
> ~/repo $ cd web
> ~/repo/web $ drush site-install profile ...

24. Managing contrib
Download, delete or update modules, themes or
profiles:> ~/repo $ composer require drupal/ds
> ~/repo $ composer remove drupal/ds
> ~/repo $ composer update drupal/ds*
> ~/repo/web $ drush ...

25. Managing core
Clean repo (git stash)
> ~/repo $ composer update drupal/core
--with-dependencies
> ~/repo $ git diff

26. Managing core
If there are no conflicts:
> ~/repo/web $ drush updb
> ~/repo $ git commit -am “Updated core”

27. Managing core
If there are:
Create a branch.
Fix conflicts (.htaccess, robots.txt,...).
Merge to master (1 commit if possible).
Done!

28. Applying patches
composer.json:
"extra": {
"patches": {
"drupal/ds": {
"Patch description #2334434": "URL to patch"
}
}
}

29. Under the hood

30. Drupal-scaffold
Part of the “scripts” attribute in composer.json
Downloads files (index.php, update.php, etc...)
Create new ones from templates
default.settings.php -> settings.php

31. Drush policy
Avoid execution of drush pm-update
Alter drush-aliases
Avoid writing in @prod *
*Needs to be added: https://github.com/drush-ops/drush/blob/8.x/examples/policy.drush.inc

32. Drush policy
Naughty developers...
Problems following workflow...

33. Grab them by the policy.
Drush policy

34. Wrapping up

35. Pros
Amazing dependency management.
All contrib out of git.
Composer hooks (pre, post, …).
Standardized.
Patches.
Also for D7.

36. Cons
Much more strict than the “classical way”
Another point of failure, composer.
If github is down…
If packagist is down…
If your internet is slow...

37. Do we commit “vendor/”?
Software distribution VS software deployment.
Robustness of deployments.
Git history.
Git size.
Best practices.
Code auditing.
Does one size fit all?

38. To git...
Robustness in deployments.
Easier and more straightforward
deployments.
Proper auditing of all production code.
Clear, accessible history of code
changes.
Small amount of extra work (once) to
ensure right process for every possible
library.
Unneeded complexity increase in
deployments, with more chance for
builds to break due to external
systems.
No auditing of code changes.
A bit smaller code repository.
Or not to git?

40. Any questions?

41. SPAM
#OPHPEN_READS
A #PHP reading club in Spanish.
http://www.isholgueras.com/blog/ophpenreads-iniciamos-el-club-de-lectura-de-libros-tecnicos
https://www.youtube.com/playlist?list=PL3NN5-oQnuvrkvOrdn1hzOHIlQOe7Gk5k

42. ¡Gracias!
Thank you!
Twitter: @Salva_bg
Blog: http://adevfromtheplains.com
#DrupalCampEs