Alex Moreno

Testing a Tome deployment

Amongst other things, I hear this quite a lot on my conversations around the subject, why decoupling Drupal, is not like you are giving away what Drupal is and overkilling with something you could do with other tools? What's the point?

So, I heard you need Drupal and memcached running in Travis, right? But you have this "little" issue that Travis/Drupal cannot connect to memcached, something like:

WD memcache: You must enable the PHP memcache (recommended) or [error] memcached extension to use memcache.inc. 
WD memcache: Failed to connect to memcache server: 127.0.0.1:11211 [error]

Before you jump into docs and tutorials on how to install memcached in Travis, probably it's already there, you just have to enable.

  [RuntimeException]

  Could not delete docroot/core/.git/hooks/applypatch-msg.sample:

  [RuntimeException]

  Source directory docroot/core has unpushed changes on the current branch:

Easy error to fix, once you know what's going on (is not always the case?).

Just upgrade your system from php 5 to php7. Drupal8 requirement.

In BLT, just edit your box/config.yml and change this line

php_version: "5.6"

to this:

php_version: "7.2"

Good old vagrant provision should do the rest of the trick. You are welcome :-)

Everything starts with a problem trying to checkout your repository master branch:

git checkout master
error: pathspec 'master' did not match any file(s) known to git.

Trying to checkout origin does not improve things, but at least is a step forward:

Working with vm’s makes everything simpler and easier. Easy to reproduce bugs, easy to reproduce features between environments and, most importantly, between developers.

Last months have been pretty busy here at BBC Worldwide with some of the projects we've been involved in.

In my case, one of the main areas I’ve been trying to improve (apart of the daily busy routine) is our devops / CI approach. The previous approach was using Chef, but it was not really adopted by the developers (which meant that after some months, the system was broken) and we were lacking some fundamental things (like integration with the production system, a real CI flow, etc…).

Software Craftsmanship is a mindset— a lifestyle that many professional developers adopt. Software craftsmen live and breathe software. They see software as a craft and are committed to do whatever they can to master their craft