<?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 Daniel Doezema's Blog</title><link>https://dan.doezema.com/tags/deployment/</link><description>Recent content in Deployment on Daniel Doezema's Blog</description><generator>Hugo</generator><language>en-US</language><copyright>&amp;copy; 2024 Daniel Doezema</copyright><lastBuildDate>Thu, 17 Jun 2010 00:00:00 +0000</lastBuildDate><atom:link href="https://dan.doezema.com/tags/deployment/index.xml" rel="self" type="application/rss+xml"/><item><title>Site Deployment with Subversion</title><link>https://dan.doezema.com/2010/06/site-deployment-with-subversion/</link><pubDate>Thu, 17 Jun 2010 00:00:00 +0000</pubDate><guid>https://dan.doezema.com/2010/06/site-deployment-with-subversion/</guid><description>&lt;p&gt;While working for a previous employer I was tasked with developing a new company &amp;ldquo;intranet&amp;rdquo; site. Changes rolled out at an aggressive rate and the process of deploying updates via FTP quickly turned into a tedious task.&lt;/p&gt;
&lt;p&gt;After a while I decided to spend some personal time thinking of ways to make whole process a bit smoother. A few of days passed as I tossed around various ideas in my head, then it hit me&amp;hellip;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Why not just checkout a working copy of the project onto the production server itself?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;






 
 
&lt;figure&gt;&lt;img src="https://dan.doezema.com/images/svn_deployment_flow.png" alt="Subversion Deployment Work Flow" class="mx-auto my-0 rounded-md" /&gt;
&lt;/figure&gt;
&lt;/p&gt;
&lt;p&gt;So simple! All I&amp;rsquo;d have to do is use the production server&amp;rsquo;s subversion client to add, update, and remove any changes &amp;ndash; deployment becomes as simple as: &lt;code&gt;$ svn up&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>