<?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 (earth2marsh)</title>
    <link>https://pinboard.in/u:earth2marsh/public/</link>
    <description>recent bookmarks from earth2marsh</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://score.dev/"/>
	<rdf:li rdf:resource="https://oam.dev/"/>
	<rdf:li rdf:resource="https://reactionwheel.net/2015/10/the-deployment-age.html"/>
	<rdf:li rdf:resource="https://deis.com/blog/2016/kubernetes-illustrated-guide/"/>
	<rdf:li rdf:resource="https://zeit.co/api#"/>
	<rdf:li rdf:resource="http://www.xaprb.com/blog/2014/11/29/code-freezes-dont-prevent-outages/"/>
	<rdf:li rdf:resource="http://engineering.remind.com/introducing-empire/"/>
	<rdf:li rdf:resource="http://eev.ee/blog/2015/09/17/the-sad-state-of-web-app-deployment/"/>
	<rdf:li rdf:resource="https://devcenter.heroku.com/articles/heroku-button"/>
	<rdf:li rdf:resource="http://bytearrays.com/shipping-code-methods-netflix/"/>
	<rdf:li rdf:resource="http://progrium.com/blog/2013/06/19/dokku-the-smallest-paas-implementation-youve-ever-seen/"/>
	<rdf:li rdf:resource="https://github.com/blog/1271-how-we-ship-github-for-windows"/>
	<rdf:li rdf:resource="http://patforna.blogspot.com/2011/04/containerless.html"/>
	<rdf:li rdf:resource="https://groups.google.com/forum/#!topic/puppet-users/GQGS996xeEw"/>
	<rdf:li rdf:resource="http://engineering.hearsaysocial.com/how-we-work"/>
	<rdf:li rdf:resource="http://briancrescimanno.com/2011/09/29/why-are-you-still-deploying-overnight/"/>
	<rdf:li rdf:resource="https://github.com/etsy/deployinator"/>
	<rdf:li rdf:resource="http://toroid.org/ams/git-website-howto"/>
	<rdf:li rdf:resource="http://engineeringblog.yelp.com/2010/09/push-it.html"/>
	<rdf:li rdf:resource="http://www.softiesonrails.com/2008/1/3/freezing-your-rails-application"/>
	<rdf:li rdf:resource="http://bitnami.org/"/>
	<rdf:li rdf:resource="http://radar.oreilly.com/archives/2007/10/operations-advantage.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://score.dev/">
    <title>Score.dev</title>
    <dc:date>2024-03-01T19:30:11+00:00</dc:date>
    <link>https://score.dev/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[another Humanitec effort
<blockquote>Score is a developer-centric and platform-agnostic workload specification. It ensures consistent configuration between local and remote environments. And it's open source.</blockquote>]]></description>
<dc:subject>deployment kubernetes platformengineering orchestration</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:4acc5f5ab262/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:kubernetes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:platformengineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:orchestration"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://oam.dev/">
    <title>OAM | Open Application Model Specification</title>
    <dc:date>2024-03-01T19:27:18+00:00</dc:date>
    <link>https://oam.dev/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Focused on application rather than container or orchestrator, Open Application Model [OAM] brings modular, extensible, and portable design for modeling application deployment with higher level yet consistent API.</blockquote>]]></description>
<dc:subject>applications orchestration kubernetes deployment platformengineering</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:551a1f622ee9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:applications"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:orchestration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:kubernetes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:platformengineering"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://reactionwheel.net/2015/10/the-deployment-age.html">
    <title>The Deployment Age | Reaction Wheel</title>
    <dc:date>2022-08-12T06:58:20+00:00</dc:date>
    <link>https://reactionwheel.net/2015/10/the-deployment-age.html</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[A lengthy overview of Carlota Perez’s theory of technological change. Progress advances in surges, and each surge has two major stages. The first is “Installation,” where a new technology irrupts and results in a speculative frenzy. The bubble pops, leading to a lot of broken hearts and empty wallets, but the frenzy leaves behind useful infrastructure. The second stage is “Deployment,” during which time the new technologies reach maturity and actually change the world.]]></description>
<dc:subject>economics technology systems deployment trends innovation cycles theory</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:dd8f316e1538/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:economics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:technology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:systems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:trends"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:innovation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:cycles"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:theory"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://deis.com/blog/2016/kubernetes-illustrated-guide/">
    <title>The Children's Illustrated Guide to Kubernetes</title>
    <dc:date>2016-06-29T21:48:24+00:00</dc:date>
    <link>https://deis.com/blog/2016/kubernetes-illustrated-guide/</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>kubernetes docker devops children guide introduction deployment</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:5fff21c02b13/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:kubernetes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:docker"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:devops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:children"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:guide"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:introduction"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deployment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://zeit.co/api#">
    <title>ZEIT – API</title>
    <dc:date>2016-06-29T05:00:03+00:00</dc:date>
    <link>https://zeit.co/api#</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>node nodejs deployment service apps neato</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:6f6390ebdf47/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:node"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:nodejs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:service"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apps"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:neato"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.xaprb.com/blog/2014/11/29/code-freezes-dont-prevent-outages/">
    <title>Why Deployment Freezes Don't Prevent Outages · Baron Schwartz's Blog</title>
    <dc:date>2015-12-07T16:31:33+00:00</dc:date>
    <link>http://www.xaprb.com/blog/2014/11/29/code-freezes-dont-prevent-outages/</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>deployment agile process management software development freeze operations</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:9b648cab192b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:agile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:process"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:freeze"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:operations"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://engineering.remind.com/introducing-empire/">
    <title>Introducing Empire: A self-hosted PaaS built on Docker &amp; Amazon ECS | Remind</title>
    <dc:date>2015-10-09T03:21:37+00:00</dc:date>
    <link>http://engineering.remind.com/introducing-empire/</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>docker aws deployment paas ecs heroku platform amazon</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:7d282c0c6138/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:docker"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:aws"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:paas"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ecs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:heroku"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:platform"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:amazon"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://eev.ee/blog/2015/09/17/the-sad-state-of-web-app-deployment/">
    <title>The sad state of web app deployment / fuzzy notepad</title>
    <dc:date>2015-09-18T05:35:27+00:00</dc:date>
    <link>http://eev.ee/blog/2015/09/17/the-sad-state-of-web-app-deployment/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Boom.]]></description>
<dc:subject>deployment webapp webdev development Ruby rant</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:4d3a03720ffc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:webapp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:webdev"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:Ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:rant"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://devcenter.heroku.com/articles/heroku-button">
    <title>Creating a 'Deploy to Heroku' Button | Heroku Dev Center</title>
    <dc:date>2015-07-06T16:18:35+00:00</dc:date>
    <link>https://devcenter.heroku.com/articles/heroku-button</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["The ‘Deploy to Heroku’ button enables users to deploy apps to Heroku without leaving the web browser, and with little or no configuration. The button is ideal for add-on providers and open-source project maintainers who wish to provide customers with a quick and easy way to deploy a Heroku app running source code that they maintain.
The button is well-suited for use in README files, and is intended to serve as a replacement to a list of manual steps typically required to configure an app."]]></description>
<dc:subject>heroku development deployment deploy</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:2f6f2ce32b7f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:heroku"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deploy"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://bytearrays.com/shipping-code-methods-netflix/">
    <title>Shipping code methods - Netflix » Programming Bytes</title>
    <dc:date>2014-09-24T22:35:40+00:00</dc:date>
    <link>http://bytearrays.com/shipping-code-methods-netflix/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[""]]></description>
<dc:subject>netflix deployment devops</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:bb89da263d60/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:netflix"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:devops"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://progrium.com/blog/2013/06/19/dokku-the-smallest-paas-implementation-youve-ever-seen/">
    <title>Dokku: The smallest PaaS implementation you've ever seen :: Jeff Lindsay</title>
    <dc:date>2013-08-09T21:22:47+00:00</dc:date>
    <link>http://progrium.com/blog/2013/06/19/dokku-the-smallest-paas-implementation-youve-ever-seen/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["Dokku is a mini-Heroku powered by Docker written in less than 100 lines of Bash. Once it’s set up on a host, you can push Heroku-compatible applications to it via Git. They’ll build using Heroku buildpacks and then run in isolated containers. The end result is your own, single-host version of Heroku.

Dokku is under 100 lines because it’s built out of several components that do most of the heavy lifting: Docker, Buildstep, and gitreceive.

Docker is a container runtime for Linux. This is a high-level container primitive that gives you a similar technology to what powers Heroku Dynos. It provides the heart of Dokku.
Buildstep uses Heroku’s open source buildpacks and is responsible for building the base images that applications are built on. You can think of it as producing the “stack” for Dokku, to borrow a concept from Heroku.
Gitreceive is a project that provides you with a git user that you can push repositories to. It also triggers a script to handle that push. This provides the push mechanism that you might be familiar with from Heroku."]]></description>
<dc:subject>deployment heroku git progrium</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:e69aec4ae4e2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:heroku"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:progrium"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/blog/1271-how-we-ship-github-for-windows">
    <title>How we ship GitHub for Windows</title>
    <dc:date>2012-09-24T18:15:33+00:00</dc:date>
    <link>https://github.com/blog/1271-how-we-ship-github-for-windows</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[""]]></description>
<dc:subject>windows ci github deployment adoption metrics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:bf3936f11856/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:windows"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ci"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:github"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:adoption"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:metrics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://patforna.blogspot.com/2011/04/containerless.html">
    <title>Patric Fornasier's Blog: ContainerLess</title>
    <dc:date>2012-01-13T20:41:15+00:00</dc:date>
    <link>http://patforna.blogspot.com/2011/04/containerless.html</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["Making this architectural change simplified our development and deployment process. It also simplified the way we thought about the application. The only price we paid was loosing the ability to deploy the application to different web server without making changes. Fortunately, this price was purely hypothetical because we had absolutely no need nor desire to use a different web server in production. On the positive side, we were now hiding the fact that we were relying on Java Servlets to realise our web functionality. In fact, seeing what some of the other communities are building (e.g. Sinatra, Node.js, etc.), I'd be tempted to try to write a web application that doesn't use Servlets at all. Part of it for fun, part of it to overcome some of the limitations inherent with the Servlet model"]]></description>
<dc:subject>java application container deployment webdev jetty</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:cac389ab039b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:java"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:application"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:container"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:webdev"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:jetty"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://groups.google.com/forum/#!topic/puppet-users/GQGS996xeEw">
    <title>Is puppet right for us? - Google Groups</title>
    <dc:date>2011-12-16T18:10:19+00:00</dc:date>
    <link>https://groups.google.com/forum/#!topic/puppet-users/GQGS996xeEw</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[nice overview of three options today]]></description>
<dc:subject>chef puppet orchestration servers deployment ops devops cfengine comparison</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:f55dab26cbfa/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:chef"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:puppet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:orchestration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:servers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:devops"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:cfengine"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:comparison"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://engineering.hearsaysocial.com/how-we-work">
    <title>How we work... - Hearsay Social Engineering</title>
    <dc:date>2011-12-16T18:05:38+00:00</dc:date>
    <link>http://engineering.hearsaysocial.com/how-we-work</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["Once you’ve built your local branch the way you want (we advocate squashing and rebasing along the way to make code review easy), we’ve built a little command-line tool (soon to be open-sourced) called “lgtm” which enables you to open a new Pull Request from the command line: just type “./lgtm create” and give it a title.  If you’re fixing a bug, it’ll show you a list of your assigned bugs in our issue/workitem tracker, Pivotal Tracker, and automatically mark this Pull Request as a fix. (this way, Github & Pivotal’s automatic integration will resolve the bug in Pivotal once the fix gets merged)."]]></description>
<dc:subject>development process git github continuous integration deployment flow</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:202ab98891e7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:process"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:github"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:continuous"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:integration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:flow"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://briancrescimanno.com/2011/09/29/why-are-you-still-deploying-overnight/">
    <title>[from sordyl] Why are you still deploying overnight? | Brian Crescimanno</title>
    <dc:date>2011-10-17T19:10:09+00:00</dc:date>
    <link>http://briancrescimanno.com/2011/09/29/why-are-you-still-deploying-overnight/</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>deployment scm configurationmanagement</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:dc7dc54bbf53/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:scm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:configurationmanagement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/etsy/deployinator">
    <title>[from sordyl] GitHub: Deployinator - deployment framework extracted from Etsy.</title>
    <dc:date>2011-08-01T13:51:04+00:00</dc:date>
    <link>https://github.com/etsy/deployinator</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>ci rubyonrails deployment</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:1dc2bf9fb5ca/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ci"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:rubyonrails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deployment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://toroid.org/ams/git-website-howto">
    <title>Using Git to manage a web site</title>
    <dc:date>2011-02-22T18:47:03+00:00</dc:date>
    <link>http://toroid.org/ams/git-website-howto</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[git push web]]></description>
<dc:subject>deployment git howto web</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:c1cd737b2ada/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:git"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:howto"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:web"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://engineeringblog.yelp.com/2010/09/push-it.html">
    <title>Yelp Engineering Blog: Push it!</title>
    <dc:date>2010-09-09T18:47:01+00:00</dc:date>
    <link>http://engineeringblog.yelp.com/2010/09/push-it.html</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["At Yelp, we push new code live every day. Pushing daily allows us to quickly prototype new features and squash bugs in a proactive manner. Because we aim to deploy new code so often, we're always looking for ways to make the process efficient and painless.  There are four main stages to the Yelp push process: code review, integration, testing, and finally, live deployment. Each step is important, and there are ways to maximize the efficiency of all of them."]]></description>
<dc:subject>yelp deploy deployment process tools continuous</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:f9a4ab1e0225/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:yelp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deploy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:process"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:continuous"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.softiesonrails.com/2008/1/3/freezing-your-rails-application">
    <title>Softies on Rails: Freezing Your Rails Application</title>
    <dc:date>2010-05-24T15:13:25+00:00</dc:date>
    <link>http://www.softiesonrails.com/2008/1/3/freezing-your-rails-application</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>version freezing freeze howto rails ruby deployment gems gem ror rake</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:163f52fb46fb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:version"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:freezing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:freeze"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:howto"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:gems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:gem"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ror"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:rake"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://bitnami.org/">
    <title>BitNami: Open Source. Simplified</title>
    <dc:date>2008-01-13T18:55:31+00:00</dc:date>
    <link>http://bitnami.org/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Easily install common opensource software stacks]]></description>
<dc:subject>installation freeware tools deployment installer opensource</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:5ef799aab90d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:installation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:freeware"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:installer"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://radar.oreilly.com/archives/2007/10/operations-advantage.html">
    <title>Operations is a competitive advantage... (Secret Sauce for Startups!)</title>
    <dc:date>2007-10-24T12:24:43+00:00</dc:date>
    <link>http://radar.oreilly.com/archives/2007/10/operations-advantage.html</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[installing and configuring an automated infrastructure management system (puppet), version control system (subversion), continuous build and test (frequently cruisecontrol.rb), software deployment (capistrano), monitoring (currently evaluating Hyperic, Ze]]></description>
<dc:subject>operations infrastructure startup management deployment scalability development article howto installation</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:63373303a21d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:operations"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:infrastructure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:startup"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deployment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:scalability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:article"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:howto"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:installation"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>