Find out more about Dropsolid and Drupal

Did you miss last week's Lunch & Learn Event about open marketing in Ghent? Dropsolid CTO Nick Veenhof explains his quick-and-dirty proof of concept for integrating the Showpad environment with the Drupal CMS.

Nick Veenhof

My reasons for joining Dropsolid

Drupal audit

How to perform a Drupal site audit

When working for a Drupal company, every once in a while a project comes your way that was built by another company, most likely without any documentation or information about its structure and architecture. The first thing to do when an takeover project lands on your plate, is to perform a full audit in order to familiarise yourself with it and to spot all potential issues. In this post, we highlight a few of the tools that we use at Dropsolid for our audits.

It is safe to say that we are currently in the midst of a Fourth Industrial Revolution, which permeates all sectors of economic and social life. Events are unfolding rapidly and the comparison with the classic three-act play - albeit at first sight perhaps rather far-fetched - is remarkably  adequate. As with any substantial narrative, there are plenty of red herrings scattered throughout the plot to lead us astray, but every turn of events does eventually lead to a climax with clearly defined winners and losers.

To work on both drupal7 and drupal8 projects, we need drush6 and drush8 on our dev environment (in my case this is ubuntu 14.04 server). I'm doing this on a clean server with a lamp stack and git installed, no drush is present yet. This can also be used to install drush8 on a server with an existing drush version, in that case only use the commands for composer and drush8.

What this will do is use 'drush6' as the default drush command for 6 and 'drush8' as the default for 8. We will be using the terminal to install everything.

Recommended articles
Drupal 8 migration strategies
Custom REST resources
Drupal 8 config management (part 1)
Dropsolid at Drupal Europe
Multiple Drush versions on one system