One important issue that comes up when undertaking a configuration management effort is how to design “the schema” for configuration management data. There are a couple of general and complementary approaches you need to know about if you’re working on this.
Here are 10 tips for teams and those who manage, administer or simply organise teams. Of course, if you are a self-managing team you should all read this list.
By default CentOS minimal install does not come with pre-configured network, here’s how to make it work.
Today, I will focus on the mix of Capistrano / Webistrano. Both of the packages are ruby on rails based, and can be easily installed using gems.
Git’s distributed approach makes it easy to push to a dedicated “deploy” branch which is being automatically fetched, but would that be possible with TFS as well?
I’ve been hearing a lot of good about Git in the last few years, from the simplicity of use, speed to decentralized repositories. Here’s a quick run through, how to install Git on a new server.
Amazon Route 53 offers DNS as a hosted service. They maintain robust DNS service for you with easy to user web interface and API.
Over the years we’ve tried several different queue/worker systems for our sites and we’d like to share our findings to help others decide on a technology.
If your VPC seems to be running slowly, here are a series of steps to rectify the situation and improve performance.
This post will walk you through the quick installation of CouchDB onto a VirtualBox instance with Chef and Vagrant.
Some people can find me a bit over-earnest in my quest for automation. I’ve finally figured out how to know whether something is worthwhile to automate.
For high-performance guaranteed delivery with EasyNetQ it's recommended that you use 'Publisher Confirms'.
I usually buy Comodo Certificates from PSW.net. It was always a pain to get it running because the information found on Comodos website are extremely outdated. If you are in pain too, here is some help.
This question amused me for a number of reasons, and I think it’s a bit of a shame it ended up closed Off Topic as it was written like a product recommendation. Let’s think about this in a little more detail.
On most of the projects I’ve worked on over the last couple of years we’ve made use of feature toggles that we used to turn pending features on and off while they were still being built but while reading Web Operations I came across another usage.
There are unfortunately ill-conceived approaches to implementing agility that can prove fatal to a continuous delivery program. In this post we’re going to take a look at one that occurs in larger organizations.
This is a Big Data talk with Monitoring as the context. The problem domain includes operational management, triaging, and business monitoring.
Chuck tries to avoid the “D” “O” word… DevOps. But he was impressed by the Allspaw talk from Velocity 09 “10+ Deploys Per Day: Dev and Ops Cooperation at Flickr“. This led him to set up a bootcamp session at Facebook and this talk is based on what he tells new developers.
Technical Debt is worth nothing if no pragmatic action is taken into code, in order to control and tackle it. To ilustrate this, we performed code refactoring on OpenKM.
This week, DZone published its 165th Refcard. The author took a few minutes to respond to some questions.
Virtualisation has changed the assumptions we can make about the physical deployment. Let me give you a few simple examples.
We all love webapps, but in the former days applications have done so much more. They were integrated into our desktops, they have done notifications in real time, they could be customized to our own needs …
Continuous Integration is now very much a central process of most agile development efforts, but it hasn’t been around all that long. But some teams are still waiting to adopt C.I... Seriously, they are!
With all the components tied together, you can’t forget a piece or deploy versions that haven’t been tested together to production.
Conceptually Maven distinguishes between snapshot versions and release versions. For top-level Maven projects that are continuously integrated it is unnatural to make this distinction.