Submitted by Jon Pugh on May 12, 2015 - 7:34pm
Well before "DevOps" was a thing, and long before DevShop existed, was "CI". Continuous Integration is a critical part of successful software development. As a web CMS, Drupal has lagged a bit behind in joining up with this world of CI.
Submitted by Jon Pugh on May 10, 2015 - 1:51pm
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.
Submitted by Jon Pugh on June 2, 2014 - 10:48pm
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.
Submitted by Jon Pugh on February 26, 2014 - 9:02am
NOTE: This blog post cross posted from http://blog.hubdrop.io/2014/02/08/the-future.html
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 hubdrop.io.
Submitted by Jon Pugh on May 6, 2013 - 12:10pm
Just going to DrupalCon to watch is awe inspiring. The amount of people there, all sharing one common goal: to learn more and grow the power of Drupal, thereby empowering themselves... it's all really inspiring stuff. There's more than a few reasons I keep coming back.
Submitted by Jon Pugh on May 2, 2013 - 9:27pm
We are as excited as everyone about heading to Portland in a few short weeks. I'm convinced it is going to be one of the most significant DrupalCons yet.
However, I was a bit disappointed when I learned that so many of our favorite tools have no session coverage at all. These aren't some niche modules, either. These modules have been used in almost all of our projects in the last few years.
Submitted by Jon Pugh on February 1, 2013 - 1:32pm
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:
Content is something that can (and should) be safely edited in real-time on your live website or application.
Submitted by Jon Pugh on January 24, 2013 - 1:51pm
We are Drupal architects and engineers that help organizations that are adopting Drupal. We believe that a dev shop transitioning to Drupal needs more than technical training, but also help with development and management strategy, site and data architecture, and server infrastructure.
As Drupal's popularity grows by leaps and bounds, web companies of all kinds are forced to adopt it. Sales teams find it incredibly easy to sell Drupal, because of all the things it offers, and all "for free". The problem is, Drupal is more than a piece of software. It is also more than the community. It is an entire culture
Submitted by Jon Pugh on January 21, 2013 - 10:38am
With 2012 over, were now approaching a full year of development of what started out as a pet project of mine: DevShop.
Development environments are complicated. There are a lot of moving parts. This is why services such as Pantheon and Acquia Hosting are so popular.
I've always used Aegir, since about version 0.3, because I loved that it removed the complexity of creating databases and users, secure passwords, settings.php files, apache vhosts, and file permissions. This frees you up to focus on the site at hand. However I noticed over the years, that despite the things aegir takes off your plate, maintaining all of the sites, files, and users that a even a small development team requires is a lot of work!
Submitted by Jon Pugh on January 16, 2013 - 9:45am
I will never manually create a database again. As long as I work in Drupal, every database I create or user I grant permissions to is managed by the Aegir hosting system.
I will never manually set up the code on my server. As long as I work in Drupal, every new site will come from a Git repository, and will be installed onto my server via DevShop and Aegir, through the web browser.