<?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 Hashbang.ca</title>
		<link>https://hashbang.ca/tag/deployment</link>
		<description>Recent content in Deployment on Hashbang.ca</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Thu, 08 Nov 2012 13:25:00 -0400</lastBuildDate>
		
			<atom:link href="https://hashbang.ca/tag/deployment/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Automating server build-out with Module::Build</title>
				<link>https://hashbang.ca/post/automating-server-build-out-with-modulebuild</link>
				<pubDate>Thu, 08 Nov 2012 13:25:00 -0400</pubDate>
				<guid>https://hashbang.ca/post/automating-server-build-out-with-modulebuild/</guid>
				<description>&lt;p&gt;At &lt;a href=&#34;http://www.pythian.com&#34;&gt;Pythian&lt;/a&gt;, we have one application that is composed of several components, the deployment of which needs to conform to our slightly peculiar server setup. Until recently, this required manually deploying each component. I did this a couple weeks ago, and it took me something like &lt;strong&gt;40 hours&lt;/strong&gt; to figure out and complete. As I went, I started reading up on &lt;code&gt;Module::Build&lt;/code&gt;, trying to figure out how to automate as much as possible. It turns out that this core module gives us a surprisingly powerful tool for customized deployment. First, it will help to understand a few aspects of how our code is deployed.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
