Let's .make fun
How to use drush .make file to maintain your codebase and avoid really strong headaches
DrupalCamp London 2016
About me
- Hi, I'm gambry
- I work at Manifesto Digital
- Things I love:
- Drupal
- PHP
- Movies
- Cooking
Common ways of setting up a Drupal project codebase
(hopefully not so common...)
Manual Download from Drupal.org
Clone Drupal GIT repo(s)
git clone http://git.drupal.org/project/drupal.git myproject
Use Drush
drush dl devel
Other or Custom ways
- Using tools
[composer, ansible, Makefile] - Scripting languages
[perl, python, ruby, bash] - Clone your own base repo
[acquia approach]
Confused?
Me too!
Drush Make
One tool to rule them all,#TheCommandOfThePower
One tool to find them,
One tool to bring them all
and in the project bind them
Drush extension able to create a ready-to-use drupal site, from a simple text file (.make) listing rules (source types, paths, destination names) and dependencies.
drush make myfile.make my-docroot
What drush make IS
- Downloads projects and libraries
- Organises downloaded files
- Patches projects and libraries
What drush make IS NOT
- Doesn't install your website
[but can prepare the codebase for installation]* - Doesn't know about (multi-)sites on your website
[but you do!]* - Doesn't take care of projects dependencies
[by itself]* - Doesn't run pre/post execution scripts
The .make file
File and Syntax
- Plain text file
- Manually created or through
drush make-generate my-drupal-website.make - YAML or .info INI syntax
- Convert the syntax with
drush make-convert my-existing-file.make
Projects & Libraries
Recursions
Includes & Overrides
Painless Patching
Patching from your .make file
- Define patch conditions
- Define patch conditions
- Define patch source
- Define patch conditions
- Define patch source
- Apply patch easily
- Define patch conditions
- Define patch source
- Apply patch easily
- Keep track of ALL your patches easily
- Define patch conditions
- Define patch source
- Apply patch easily
- Keep track of ALL your patches easily
- Document patches easily
- Define patch conditions
- Define patch source
- Apply patch easily
- Keep track of ALL your patches easily
- Document patches easily
You have the control of the workflow and the system
- Define patch conditions
- Define patch source
- Apply patch easily
- Keep track of ALL your patches easily
- Document patches easily
You have the control of the workflow and the system
and NOT the other way round!!!
Tips and Tricks
Everyday examples, suggestions, ideas
.make your workflow
base.make
prod.make
test.make
dev.make
.make your workflow (2)
.gitignore:
!docroot/sites
docroot/sites/*
!docroot/sites/all
docroot/sites/all/*
!docroot/sites/all/modules
docroot/sites/all/modules/*
!docroot/sites/all/modules/custom
!docroot/sites/all/modules/feature
Controlling recursion
do_recursion: 0
--no-recursion
Multisites
contrib_destination: "sites/site2.co.uk"
Patching issue
type = git
Custom .htaccess?
Patch the core!
Thank you!
@gambry
@DrupalCampLDN
#TheCommandOfThePower
Questions or Lunch???
@gambry
@DrupalCampLDN
#TheCommandOfThePower