A friend recently asked my opinion on the DevShop Drupal project. A dev-ops utility for Drupal. And then I recalled why I didn’t give it a shot earlier, and help the fellow developers via a DevShop review.

It is a really nice effort by the developers behind it. They have the right vision and approach in mind. However, it is only for Drupal. As a full stack developer and devops engineer I usually am on the lookout for something that caters to my requirements across various web platforms and technologies. For instance, at Axelerant, I work a lot with Ruby on Rails.

While DevShop is well architectured, and has nice process controls, I still feel it lacks a lot of essential features. Here is a short list of the Pros and Cons that I feel this utility still needs to address. This is by no means an in-depth review. I am only focusing on features that affect my workflow.

Medhamsh’s DevShop Review…

DevShop Pros:

  • One stop solution for drupal release management, hosting.
  • Can create projects on shared hosting.
  • Can attach multiple servers and maintain them (Like WHM/Cpanel)
  • Automatic installation of profiles by detecting them in code.
  • Sync databases from source to destination
  • Online file browser

DevShop Cons:

  • It is a pain in the a** to setup.
  • Works only on Ubuntu 12.04 without massive hacks. Ugh.
  • Most of the things don’t work, even though they appear to in the frontend panel.
  • No files sync across instances.
  • No proper user management.
  • If you are a sysadmin and want to maintain a couple of servers, then this is for you.
  • Lack of proper user management makes it very cumbersome to implement DevOps best practices.
  • Nearly impossible to give shell access.
  • No isolation of projects because they are hosted under a directory. /var/aegir/projects/*

As I mentioned above, a lot more could go in pros and cons but that will need a much more detailed review.

Despite all the cons, I feel it is a very good first effort by the developers, especially in terms of workflow. It would be great to hear from the maintainer of the project, Jon Pugh, or other committers on what they think of this list.

This article was originally published May 26, 2014. It has been updated since then for clarity.