<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Deployment on vnykmshr</title><link>https://blog.vnykmshr.com/writing/tags/deployment/</link><description>Recent content in Deployment on vnykmshr</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 15 Jul 2013 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.vnykmshr.com/writing/tags/deployment/index.xml" rel="self" type="application/rss+xml"/><item><title>Zero-downtime deploys</title><link>https://blog.vnykmshr.com/writing/zero-downtime-deploys/</link><pubDate>Mon, 15 Jul 2013 00:00:00 +0000</pubDate><guid>https://blog.vnykmshr.com/writing/zero-downtime-deploys/</guid><description>&lt;p&gt;I deploy everything from the terminal. No web interface, no CI service, no dashboard with green buttons. Just &lt;code&gt;deploy production&lt;/code&gt; from my laptop, and the code goes live.&lt;/p&gt;
&lt;p&gt;The setup is two pieces. A bash script that handles the remote work &amp;ndash; SSH in, pull the latest code, run hooks. And a Node.js process that watches a file on the server and reloads the app cluster when the file changes. Between them, they do zero-downtime deploys in under ten seconds.&lt;/p&gt;</description></item></channel></rss>