<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (jm)</title>
    <link>https://pinboard.in/u:jm/public/</link>
    <description>recent bookmarks from jm</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://curlpipesh.tumblr.com/"/>
	<rdf:li rdf:resource="http://forty9ten.com/post/64676776664/avoiding-chef-suck-with-auto-scaling-groups"/>
	<rdf:li rdf:resource="https://speakerdeck.com/jtimberman/chef-vault"/>
	<rdf:li rdf:resource="http://blog.pagerduty.com/2013/11/chef-testing-pagerduty/"/>
	<rdf:li rdf:resource="http://workstuff.tumblr.com/post/50911984233/some-tips-on-getting-started-with-vagrant-and-chef"/>
	<rdf:li rdf:resource="https://speakerdeck.com/nathenharvey/testing-your-automation"/>
	<rdf:li rdf:resource="http://serverspec.org/"/>
	<rdf:li rdf:resource="http://www.solowizard.com/"/>
	<rdf:li rdf:resource="http://kent.spillner.org/blog/books/2012/03/28/test-driven-infrastructure-with-chef.html"/>
	<rdf:li rdf:resource="https://github.com/infochimps-labs/ironfan/wiki/walkthrough-web"/>
	<rdf:li rdf:resource="http://omniti.com/seeds/seeds-our-experiences-with-chef-adoption-challenges"/>
	<rdf:li rdf:resource="http://awsadvent.tumblr.com/"/>
	<rdf:li rdf:resource="http://blog.lusis.org/blog/2012/12/17/how-we-vagrant/"/>
	<rdf:li rdf:resource="http://blog.brattyredhead.com/blog/2012/12/13/shell-scripts-are-like-gremlins/"/>
	<rdf:li rdf:resource="http://techblog.netflix.com/2011/08/building-with-legos.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://curlpipesh.tumblr.com/">
    <title>curl | sh</title>
    <dc:date>2014-11-03T15:07:04+00:00</dc:date>
    <link>http://curlpipesh.tumblr.com/</link>
    <dc:creator>jm</dc:creator><description><![CDATA['People telling people to execute arbitrary code over the network. Run code from our servers as root. But HTTPS, so it’s no biggie.'

YES.]]></description>
<dc:subject>humor sysadmin ops security curl bash npm rvm chef</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:a5083a15872a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:humor"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sysadmin"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:curl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:bash"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:npm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:rvm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:chef"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://forty9ten.com/post/64676776664/avoiding-chef-suck-with-auto-scaling-groups">
    <title>Avoiding Chef-Suck with Auto Scaling Groups - forty9ten</title>
    <dc:date>2014-09-23T13:43:29+00:00</dc:date>
    <link>http://forty9ten.com/post/64676776664/avoiding-chef-suck-with-auto-scaling-groups</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Some common problems which arise using Chef with ASGs in EC2, and how these guys avoided it -- they stopped using Chef for service provisioning, and instead baked AMIs when a new version was released.  ASGs using pre-baked AMIs definitely works well so this makes good sense IMO.]]></description>
<dc:subject>infrastructure chef ops asg auto-scaling ec2 provisioning deployment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:2c44711b992b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:infrastructure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:chef"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:asg"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:auto-scaling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ec2"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:provisioning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:deployment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://speakerdeck.com/jtimberman/chef-vault">
    <title>Chef Vault</title>
    <dc:date>2014-06-27T14:21:06+00:00</dc:date>
    <link>https://speakerdeck.com/jtimberman/chef-vault</link>
    <dc:creator>jm</dc:creator><description><![CDATA[A way to securely store secrets (auth details, API keys, etc.) in Chef]]></description>
<dc:subject>chef storage knife authorisation api-keys security encryption</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:16c5bf0aa66a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:chef"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:storage"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:knife"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:authorisation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:api-keys"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:encryption"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.pagerduty.com/2013/11/chef-testing-pagerduty/">
    <title>Chef Testing at PagerDuty</title>
    <dc:date>2013-12-06T09:47:35+00:00</dc:date>
    <link>http://blog.pagerduty.com/2013/11/chef-testing-pagerduty/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Good article on how PagerDuty test their chef changes -- lint, unit tests using ChefSpec, integ tests and their "Failure Friday" game days]]></description>
<dc:subject>testing chef ops devops chefspec game-days pagerduty</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:71cad664b1e4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:chef"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:devops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:chefspec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:game-days"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:pagerduty"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://workstuff.tumblr.com/post/50911984233/some-tips-on-getting-started-with-vagrant-and-chef">
    <title>Vagrant and Chef to provision dev test environments</title>
    <dc:date>2013-06-12T09:22:58+00:00</dc:date>
    <link>http://workstuff.tumblr.com/post/50911984233/some-tips-on-getting-started-with-vagrant-and-chef</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>We have recently switched from a manually configured development environment to a nearly fully automated one using Vagrant, Chef, and a few other tools. With this transition, we’ve moved to an environment where data on the dev boxes is considered disposable and only what’s checked into the SCM is “real”. This is where we’ve always wanted to be, but without the ability to easily rebuild the dev environment from scratch, it’s hard to internalize this behavior pattern.</blockquote>

]]></description>
<dc:subject>dev osx chef vagrant testing vms coding</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:f77dce9550ae/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:dev"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:osx"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:chef"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:vagrant"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:vms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:coding"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://speakerdeck.com/nathenharvey/testing-your-automation">
    <title>Testing Your Automation [slides]</title>
    <dc:date>2013-04-08T09:50:19+00:00</dc:date>
    <link>https://speakerdeck.com/nathenharvey/testing-your-automation</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Test-driven infrastructure, using Chef -- slides from Big Ruby 2013.  Tools used: foodcritic (lol), Chefspec, minitest-chef-handler, fauxhai, cucumber chef.  This is really good to see -- TDD applied to ops.  Video at: http://confreaks.com/videos/2309-bigruby2013-testing-your-automation-ttd-for-chef-cookbooks]]></description>
<dc:subject>devops ops chef automation testing tdd infrastructure provisioning deployment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:a89320ec7528/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:devops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:chef"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:automation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tdd"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:infrastructure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:provisioning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:deployment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://serverspec.org/">
    <title>serverspec - unit tests for servers</title>
    <dc:date>2013-04-02T13:08:58+00:00</dc:date>
    <link>http://serverspec.org/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>With serverspec, you can write RSpec tests for checking your servers are provisioned correctly.  Serverspec tests your servers' actual state through SSH access, so you don't need to install any agent softwares on your servers and can use any provisioning tools, Puppet, Chef, CFEngine and so on.</blockquote>

(via Dave Doran)]]></description>
<dc:subject>via:dave-doran puppet testing chef cfengine unit-testing ops provisioning serverspec rspec ruby</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:5fcd60f18681/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:via:dave-doran"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:puppet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:chef"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cfengine"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:unit-testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:provisioning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:serverspec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:rspec"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ruby"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.solowizard.com/">
    <title>SoloWizard</title>
    <dc:date>2013-03-14T14:20:51+00:00</dc:date>
    <link>http://www.solowizard.com/</link>
    <dc:creator>jm</dc:creator><description><![CDATA['bootstrap an OSX development machine with a one-liner'.

<blockquote>Many teams use chef to manage their production machines, but developers often build their development boxes by hand. SoloWizard makes it painless to create a configurable chef solo script to get your development machine humming: mysql, sublime text, .bash_profile tweaks to OS-X settings - it's all there!</blockquote>]]></description>
<dc:subject>osx chef mac build-out ops macosx deployment developers desktops laptops mysql rabbitmq activemq nginx</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:c9a860892e4c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:osx"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:chef"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:mac"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:build-out"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:macosx"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:developers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:desktops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:laptops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:mysql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:rabbitmq"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:activemq"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:nginx"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kent.spillner.org/blog/books/2012/03/28/test-driven-infrastructure-with-chef.html">
    <title>Test-Driven Infrastructure with Chef</title>
    <dc:date>2013-03-06T22:29:40+00:00</dc:date>
    <link>http://kent.spillner.org/blog/books/2012/03/28/test-driven-infrastructure-with-chef.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Interesting idea.

<blockquote>The book introduces “Infrastructure as Code,” test-driven development, Chef, and cucumber-chef, and then proceeds to a simple example using Chef to provision a shared Linux server. The recipes for the server are developed test-first, demonstrating both the technique and the workflow.</blockquote>

]]></description>
<dc:subject>tdd chef server provisioning build deploy linux coding ops sysadmin</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:60b79ff1f4ce/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:tdd"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:chef"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:server"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:provisioning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:build"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:deploy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:linux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:coding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sysadmin"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/infochimps-labs/ironfan/wiki/walkthrough-web">
    <title>Ironfan</title>
    <dc:date>2013-01-27T21:11:16+00:00</dc:date>
    <link>https://github.com/infochimps-labs/ironfan/wiki/walkthrough-web</link>
    <dc:creator>jm</dc:creator><description><![CDATA['an expressive toolset for constructing scalable, resilient [service] architectures. It works in the cloud, in the data center, and on your laptop, and it makes your system diagram visible and inevitable. Inevitable systems coordinate automatically to interconnect, removing the hassle of manual configuration of connection points (and the associated danger of human error).'  Looks like a pretty neat cluster deployment tool; driven from a single configuration file, using Chef, integrating closely with AWS and providing many useful additional features]]></description>
<dc:subject>chef deployment clusters knife services aws ec2 ops ironfan demo</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:ed73e23aae92/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:chef"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:clusters"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:knife"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:services"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aws"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ec2"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ironfan"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:demo"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://omniti.com/seeds/seeds-our-experiences-with-chef-adoption-challenges">
    <title>OmniTI's Experiences Adopting Chef</title>
    <dc:date>2013-01-14T14:01:53+00:00</dc:date>
    <link>http://omniti.com/seeds/seeds-our-experiences-with-chef-adoption-challenges</link>
    <dc:creator>jm</dc:creator><description><![CDATA[A good, in-depth writeup of OmniTI's best practices with respect to build-out of multiple customer deployments, using multi-tenant Chef from a version-controlled repo.  Good suggestions, and I am really looking forward to this bit:

'Chef tries to turn your system configuration into code. That means you now inherit all the woes of software engineering: making changes in a coordinated manner and ensuring that changes integrate well are now an even greater concern. In part three of this series, we’ll look at applying software quality assurance and release management  practices to Chef cookbooks and roles.']]></description>
<dc:subject>chef deployment ops omniti systems vagrant automation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:07d0ae11b7e7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:chef"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:omniti"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:systems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:vagrant"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:automation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://awsadvent.tumblr.com/">
    <title>AWS Advent 2012</title>
    <dc:date>2012-12-20T14:42:15+00:00</dc:date>
    <link>http://awsadvent.tumblr.com/</link>
    <dc:creator>jm</dc:creator><description><![CDATA['an annual exploration of Amazon Web Services.'  Some great hacks here]]></description>
<dc:subject>aws amazon advent sysadmin s3 ec2 chef puppet ops</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:c1153955381e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aws"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:amazon"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:advent"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sysadmin"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:s3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ec2"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:chef"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:puppet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:ops"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.lusis.org/blog/2012/12/17/how-we-vagrant/">
    <title>How We Vagrant</title>
    <dc:date>2012-12-19T15:03:08+00:00</dc:date>
    <link>http://blog.lusis.org/blog/2012/12/17/how-we-vagrant/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[the enStratus “solo installer”; what they use for one-box testing, staging, and customer stack deployment, using chef-solo and Vagrant]]></description>
<dc:subject>chef virtualization vagrant chef-solo deployment enstratus cluster stack</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:f289ba29aa8b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:chef"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:virtualization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:vagrant"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:chef-solo"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:enstratus"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cluster"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:stack"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.brattyredhead.com/blog/2012/12/13/shell-scripts-are-like-gremlins/">
    <title>Shell Scripts Are Like Gremlins</title>
    <dc:date>2012-12-14T14:55:24+00:00</dc:date>
    <link>http://blog.brattyredhead.com/blog/2012/12/13/shell-scripts-are-like-gremlins/</link>
    <dc:creator>jm</dc:creator><description><![CDATA[<blockquote>Shell Scripts are like Gremlins. You start out with one adorably cute shell script. You commented it and it does one thing really well. It’s easy to read, everyone can use it. It’s awesome! Then you accidentally spill some water on it, or feed it late one night and omgwtf is happening!?</blockquote>

+1.  I have to wean myself off the habit of automating with shell scripts where a clean, well-unit-tested piece of code would work better.]]></description>
<dc:subject>shell-scripts scripting coding automation sysadmin devops chef deployment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:3ed33353d153/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:shell-scripts"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:scripting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:coding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:automation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:sysadmin"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:devops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:chef"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:deployment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://techblog.netflix.com/2011/08/building-with-legos.html">
    <title>Building with Legos</title>
    <dc:date>2011-08-15T12:58:50+00:00</dc:date>
    <link>http://techblog.netflix.com/2011/08/building-with-legos.html</link>
    <dc:creator>jm</dc:creator><description><![CDATA[Netflix tech blog on how they deploy their services.  Notably, they avoid the Puppet/Chef approach, citing these reasons: 'One is that it eliminates a number of dependencies in the production environment: a master control server, package repository and client scripts on the servers, network permissions to talk to all of these. Another is that it guarantees that what we test in the test environment is the EXACT same thing that is deployed in production; there is very little chance of configuration or other creep/bit rot. Finally, it means that there is no way for people to change or install things in the production environment (this may seem like a really harsh restriction, but if you can build a new AMI fast enough it doesn't really make a difference).']]></description>
<dc:subject>devops cloud aws netflix puppet chef deployment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jm/b:a7e9bb6fa987/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:devops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:cloud"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:aws"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:netflix"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:puppet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:chef"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jm/t:deployment"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>