DevOps, it’s a term that has been used a lot lately. It specifically began as a term to define the need for computer programmers, and their IT staff, to work closely together. So that code, releases, and hardware changes all happened together in harmony. It was a movement to raise awareness that the old days, of developers tossing code to the operations team, and then the operations team complaining that the code didn’t work … simply wasn’t not a sustainable model for web development. So much of the code systems themselves now needed to be tightly locked with the infrastructure.

Over time, the term also came to define another meaning as well. Specifically in smaller shops, where it wasn’t just that the operations and development teams were working closely together, but where it was the same team. Sometimes a single person might be in charge of operations while also being a developer part-time. In others it might be that the duties are divided out among various people.

Regardless of what kind of DevOps environment you are working within, it’s important for developers to be as involved as possible with the infrastructure, deployment, and overall operations management. We’ve brought together four experts in the field, to talk to you about managing code dependencies with Composer, best ways to deploy your code, managing development environments with Vagrant, and how to automate your infrastructure in the cloud.