Presenting Provision 4.x CLI Developer Sneak Peek at DrupalNYC

I presented at the first Drupal NYC Meetup of the year!

I've been hard at work building a new Provision: the command-line interface for Aegir. We are moving off Drush commands into our own CLI built in Symfony. The tool is finally a working MVP, so I figured it's time to spread the word! 

First I give a bit of background on the Aegir project and my goals for the project which can be summed up in one word: easy.

Cultivating the Aegir Community at DrupalGovCon17

UPDATESlides and Video of the session are now available.

Every time there is a big DrupalCamp or Con we submit sessions thinking we will talk about our open source hosting and testing platform, DevShop. The specific theme for each talk usually aligns with whatever the latest features are, or is just a general (boring) overview of the features.

Aegir on Docker: Faster Development, Better Testing, Easier Deployment.

In the last few days We've been able to get Aegir working in a docker container.

See for the code and for the images.  There are example docker-compose.yml file in the codebase that you can use to launch aegir really quickly.

Collaborative Configuration with DevShop, Aegir & Ansible Galaxy

With the release of the first beta of DevShop we completed the switch to using Ansible Galaxy Roles, which are open source, collaborative infrastructure. Up until the last alpha release, DevShop installed via it's own custom playbook.

Now, each component of DevShop is broken out into separate Ansible Galaxy Roles, extending Jeff Geerling's playbooks.

Our Mission is Easy Open Source Infrastructure

Software evolves over time as any technology. When people invent new things, they usually launch new businesses for those inventions. They patent them. They protect their intellectual property for as long as they can.

At some point, proprietary technology becomes so prolific, that the need for agreed upon standards becomes necessary. Edison wouldn't have sold nearly as many light bulbs if they didn't standardize the size of the sockets and the shape of the two prongs, among other more important things like voltage.

Think. Drop. Repeat.

Our new slogan says a lot to us.

The name "ThinkDrop" sounded good to me when it first came to me for a few reasons.  

"Think: Drupal!" comes to mind.

But to me, "Drop" also means "Release".

The fastest way to make great software is to quickly iterate through the cycles, releasing early and releasing often, collecting feedback all the way through.

Think. Drop. Repeat.

DevShop Workshop & Sprints at DrupalCon Los Angeles

I'm headed to DrupalCon on Monday morning, and hope to spend most of my time recruiting users and sprinters to DevShop development.

The DrupalCon sprints are an amazing opportunity to work together with people in person. Despite being very remote-oriented, there really is no replacement for face to face work, especially when it comes to complex projects like DevShop.

There are a number of opportunities this week to come learn about devshop.



Bats of a Feather: HubDrop, DevShop, & Aegir at DrupalCon Austin

I'm on the plane headed to my 4th DrupalCon, and this one is looking like a good time.  

So much is happening this year. Drupal 8 is getting closer and closer to release, more and more Drupal businesses and services are being launched, and we continue to develop our Drupal products.

While my session on DevShop wasn't accepted, I am personally involved in a lot of BoF sessions this year.

Introducing bridging the gap between and GitHub


This project is simply something I wanted to do. No one paid for it. I built it in my spare time as a way to refine the knowledge I learned over the last few years about Symfony, Vagrant, and Chef. I want to grow this tool, but it takes time and a server, which both == money.

So I'm opening up a GitTip account to raise funding for development of

But before I do that, I wanted to formally introduce HubDrop to the Drupal aocmmunity.

Defining "Content": Treating Drupal as a CMF

Time and time again the debate about "what is content" and "what is configuration" comes up. I think not often enough we talk about it in words but not in the intentions of what you are building. This article is just about content, because everything else is just code.

First of all, what is "Content", really? It recently has become crystal clear to me: