vrijdag 15 maart 2013


The Berkshelf is a location on your local disk which contains the cookbooks you have installed and their dependencies. By default, The Berkshelf is located at ~/.berkshelf but this can be altered by setting the environment variable BERKSHELF_PATH. Berkshelf stores every version of a cookbook that you have ever installed. This is the same pattern found with RubyGems where once you have resolved and installed a gem, you will have that gem and it’s dependencies until you delete it. This central location is not the typical pattern of cookbook storage that you may be used to with Chef. The traditional pattern is to place all of your cookbooks in a directory called cookbooks or site-cookbooks within your Chef Repository. We do have all of our cookbooks in one central place, it’s just not the Chef Repository and they’re stored within directories named using the convention {name}-{version}.

via Delicious http://berkshelf.com/

maandag 4 maart 2013

Pacemaker and HAProxy: Preventing Single Points of Failure - IT and ME

In the past, I’ve shared how we use HAProxy to help increase uptime and distribute load among any number of web servers. HAProxy is an amazing tool, and I can’t thank the author, Willy Tarreau, enough for making it available and open source. Of course, while HAProxy has proven to be extremely stable in production and we’ve never had an issue with it at all, it does present its own single point of failure. If your HAProxy server dies, everything that relies on HAProxy will go down with it. While I am not at all concerned about HAProxy itself crashing, I am concerned about a gamma ray hitting the CPU at just the wrong moment and nuking the whole thing.

via Delicious http://itand.me/41901523

zaterdag 2 maart 2013


via Delicious http://nzb.su/

jonnyboy/newznab-tmux · GitHub

Scripts for Newznab

via Delicious https://github.com/jonnyboy/newznab-tmux#readme