I’ve recently decided to take the plunge and move from Apache and Mod_WSGI to Nginx and FastCGI – I was amazed at how simple it was! To get Edison up and running under Nginx as a fast-cgi Deamon, you just need to follow these steps...
Campfire is a really sexy HTTP based chat system provided by 37 signals. I've found a clone-type application written by @maccman on Github, called Holla. I'm gonna have a go at installing it on Ubuntu 10.04.
Here’s a bunch of upcoming talks, courses, conferences, things and stuff, which I reckon might be worth checking out.
Scp is slow, that’s a known fact. Known and so annoying that someone tried to fix it by producing the hpn-ssh patch.
Until fairly recently, Willie Wheeler thought of devops mostly in terms of various sorts of automation: build, test, deployment, operations and SDLC. If automation is the how, then integration is the what.
9 tips on when to do (or not do) certain things in secure shell. Some 'do's' include using SSH agents and multiple keys. Some 'don'ts' include leaving your agents running after you log out and copying your private key around.
I think there are a handful of best practices for application deployments which can pretty much extend across almost all applications, certainly all the ones we were talking about. Here are some of what I would define as best practices for application deployments.
I had a failed deployment. I know how to handle complex deployments, and didn’t follow my own advice. I'll explain it so you can learn from my mistakes.
I've started using the mongrel2 web server and set it up with graphite on the same server. So I could just proxy all graphite requests from mongrel2 to Apache, or I could do try to get mongrel2 to talk wsgi to graphite directly. I chose latter and here’s how I did it.
Over some certain pieces of infrastructure (or infrastructure services) accumulate some feature or functionality that is not automated or documented. Here is how you prevent that...
Eric Minick gives us 5 takeaways we can learn about deployment automation based on his past experiences with another super-streamlined process: Amazon Prime.
In this article we’re going to step away from the keyboard and get architectural. But no ivory towers here. I’m going to give you something that will get you out of lots of pointless meetings. Got your attention yet? Good!
This blogpost is a first stab at providing a structure to codify devops practices. The wording, descriptions are pretty much work in progress, but I found them important enough to share to get your feedback.
We’ll move past the fluffy characterization involving developers and operations working together joyously—not to mention the outright wrong characterization of one superrole that does it all—and get to the heart of what devops is really about.
A few folks suggested to me that a bit more information on the built-in properties and property scoping for uDeploy would be handy. Message received, and we’ll flesh out the documentation on that front. In the meantime, here’s a quick list of the automaticly available properties.
A new uDeploy release comes fast and furious this week with server log visibility, locking, and post-processing improvements
The BIND-DLZ project publishes an excellent set of performance testing tools which make it easy to generate a lot of fake DNS data for a variety of DNS server types. I have even extended this excellent tool set by creating a few new “writer” modules...
Here is a list of three major types of elasticity that I have implemented / experienced so far. I'm also setting up a unit and functional testing environment that will re-utilize some of our architecture.
There can be friction between the various ways agile teams work, and it seems that the root of the conflict between agile and continuous delivery is the approach to making software "ready for release."
The first in a news series of blog posts by DevOps godfather, Patrick DuBois, will look at the integration and options within Nagios with reference to his infrastructure at Atlassian, where they must monitor about 10,000 websites.
Maven doesn’t like it when you use different verison numbers to the Maven standard format. I’m not “Maven bashing”, it’s just that this particular problem doesn’t have quite the elegant solution I was looking for. I do appreciate Maven, honestly.
If you're already using Vagrant to manage your VirtualBox VMs, then you probably have realized already how annoying is to keep the VBox guest additions up to date in your VMs. We'll help you fix this issue...
Here's a quick rundown of 6 types of monitoring for your infrastructure. Yes, there are six, and a few that you might not have thought of.
Joe Miller needed a simple mechanism to build native packages on the relevant platforms, ie: .deb's on debian and .rpm on redhat/centos. He ended up using a combination of Vagrant and some homegrown tools such as Bunchr.
The general best practice is to add an additional element for each service tier, also know as N+1 redundancy. This approach is straight forward, but many people would actually be surprised by how often these schemes fail.