<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: 5 Tips for Deploying Background Jobs in Ruby on Rails</title>
	<atom:link href="http://www.engineyard.com/blog/2009/5-tips-for-deploying-background-jobs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.engineyard.com/blog/2009/5-tips-for-deploying-background-jobs/</link>
	<description></description>
	<lastBuildDate>Wed, 08 Feb 2012 12:12:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Todd</title>
		<link>http://www.engineyard.com/blog/2009/5-tips-for-deploying-background-jobs/comment-page-1/#comment-41495</link>
		<dc:creator>Todd</dc:creator>
		<pubDate>Tue, 16 Mar 2010 16:53:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.engineyard.com/blog/?p=1884#comment-41495</guid>
		<description>Ever get a fix for this?  Same issue </description>
		<content:encoded><![CDATA[<p>Ever get a fix for this?  Same issue</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sandeep Ghael</title>
		<link>http://www.engineyard.com/blog/2009/5-tips-for-deploying-background-jobs/comment-page-1/#comment-40241</link>
		<dc:creator>Sandeep Ghael</dc:creator>
		<pubDate>Fri, 29 Jan 2010 04:57:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.engineyard.com/blog/?p=1884#comment-40241</guid>
		<description>one more thought:  Monitor your processes that manage background tasks using something like Webmin.  That&#039;s how we monitor our Delayed Jobs rake taks at Active Interview, to make sure everything is actually running smoothly: 
 
&lt;a href=&quot;http://blog.activeinterview.com/post/2010/01/28/use-webmin-to-monitor-rails-delayed-job-or-anything/&quot; target=&quot;_blank&quot;&gt;http://blog.activeinterview.com/post/2010/01/28/u...&lt;/a&gt; </description>
		<content:encoded><![CDATA[<p>one more thought:  Monitor your processes that manage background tasks using something like Webmin.  That&#039;s how we monitor our Delayed Jobs rake taks at Active Interview, to make sure everything is actually running smoothly: </p>
<p><a href="http://blog.activeinterview.com/post/2010/01/28/use-webmin-to-monitor-rails-delayed-job-or-anything/" target="_blank">http://blog.activeinterview.com/post/2010/01/28/u&#8230;</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Walton</title>
		<link>http://www.engineyard.com/blog/2009/5-tips-for-deploying-background-jobs/comment-page-1/#comment-37469</link>
		<dc:creator>Bill Walton</dc:creator>
		<pubDate>Mon, 02 Nov 2009 21:46:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.engineyard.com/blog/?p=1884#comment-37469</guid>
		<description>Has any one here gotten Bj to setup on a Windows XP box?  I&#039;ve tried both gem and plugin and neither is working.  I can share details, for sure, but don&#039;t want to take up bandwidth unless there&#039; s someone out there interested or experienced. 
 
Thanks, 
Bill </description>
		<content:encoded><![CDATA[<p>Has any one here gotten Bj to setup on a Windows XP box?  I&#039;ve tried both gem and plugin and neither is working.  I can share details, for sure, but don&#039;t want to take up bandwidth unless there&#039; s someone out there interested or experienced. </p>
<p>Thanks,<br />
Bill</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew</title>
		<link>http://www.engineyard.com/blog/2009/5-tips-for-deploying-background-jobs/comment-page-1/#comment-31145</link>
		<dc:creator>Matthew</dc:creator>
		<pubDate>Wed, 21 Oct 2009 19:10:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.engineyard.com/blog/?p=1884#comment-31145</guid>
		<description>I believe the wiki now has a good overview of each fork, i personally use collectiveidea </description>
		<content:encoded><![CDATA[<p>I believe the wiki now has a good overview of each fork, i personally use collectiveidea</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: machvee</title>
		<link>http://www.engineyard.com/blog/2009/5-tips-for-deploying-background-jobs/comment-page-1/#comment-30991</link>
		<dc:creator>machvee</dc:creator>
		<pubDate>Wed, 21 Oct 2009 14:12:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.engineyard.com/blog/?p=1884#comment-30991</guid>
		<description>Any good solutions to getting a dedicated instance of delayed_job job_runner to execute only certain locally submitted jobs?  We have an upload task that reads from a local file, and as we have no shared disk on EY, has to run on the app instance in which the user originally uploaded.    </description>
		<content:encoded><![CDATA[<p>Any good solutions to getting a dedicated instance of delayed_job job_runner to execute only certain locally submitted jobs?  We have an upload task that reads from a local file, and as we have no shared disk on EY, has to run on the app instance in which the user originally uploaded.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: themcgruff</title>
		<link>http://www.engineyard.com/blog/2009/5-tips-for-deploying-background-jobs/comment-page-1/#comment-30565</link>
		<dc:creator>themcgruff</dc:creator>
		<pubDate>Tue, 20 Oct 2009 20:25:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.engineyard.com/blog/?p=1884#comment-30565</guid>
		<description>Hey Todd, 
 
There isn&#039;t anything special that should be required.  There is logic in most of the libraries to handle multiple hosts processing jobs.  The main thing to remember is that they need to be deployed on the same code base and utilize the same database (since this is where the jobs live and are locked).  For instance we have a number of customers using BJ configured to run under cron on multiple slices.  Additionally we have customers running DJ (workers) on multiple slices.  The setup is the same each time. </description>
		<content:encoded><![CDATA[<p>Hey Todd, </p>
<p>There isn&#039;t anything special that should be required.  There is logic in most of the libraries to handle multiple hosts processing jobs.  The main thing to remember is that they need to be deployed on the same code base and utilize the same database (since this is where the jobs live and are locked).  For instance we have a number of customers using BJ configured to run under cron on multiple slices.  Additionally we have customers running DJ (workers) on multiple slices.  The setup is the same each time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd</title>
		<link>http://www.engineyard.com/blog/2009/5-tips-for-deploying-background-jobs/comment-page-1/#comment-30551</link>
		<dc:creator>Todd</dc:creator>
		<pubDate>Tue, 20 Oct 2009 19:58:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.engineyard.com/blog/?p=1884#comment-30551</guid>
		<description>Any good tutorials on running multiple backgroundjob instances across multiple servers to handle huge backend needs?  Thanks! </description>
		<content:encoded><![CDATA[<p>Any good tutorials on running multiple backgroundjob instances across multiple servers to handle huge backend needs?  Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: claudiob</title>
		<link>http://www.engineyard.com/blog/2009/5-tips-for-deploying-background-jobs/comment-page-1/#comment-18783</link>
		<dc:creator>claudiob</dc:creator>
		<pubDate>Fri, 18 Sep 2009 00:42:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.engineyard.com/blog/?p=1884#comment-18783</guid>
		<description>Ambethia, you just made my day! I had that some problem and your fork solved it! 
Now I&#039;m gonna follow you on github&#8230; I had to build the gem by myself since you had it not working. I guess you should remove the whole rails folder in your spec, so that the gem is fine and small. It worked for me (using your code). </description>
		<content:encoded><![CDATA[<p>Ambethia, you just made my day! I had that some problem and your fork solved it!<br />
Now I&#039;m gonna follow you on github&hellip; I had to build the gem by myself since you had it not working. I guess you should remove the whole rails folder in your spec, so that the gem is fine and small. It worked for me (using your code).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ambethia</title>
		<link>http://www.engineyard.com/blog/2009/5-tips-for-deploying-background-jobs/comment-page-1/#comment-18778</link>
		<dc:creator>ambethia</dc:creator>
		<pubDate>Thu, 17 Sep 2009 23:37:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.engineyard.com/blog/?p=1884#comment-18778</guid>
		<description>Actually, some knee-deep googling turned up a solution, applied here: &lt;a href=&quot;http://github.com/ambethia/bj&quot; target=&quot;_blank&quot;&gt;http://github.com/ambethia/bj&lt;/a&gt; </description>
		<content:encoded><![CDATA[<p>Actually, some knee-deep googling turned up a solution, applied here: <a href="http://github.com/ambethia/bj" target="_blank">http://github.com/ambethia/bj</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ambethia</title>
		<link>http://www.engineyard.com/blog/2009/5-tips-for-deploying-background-jobs/comment-page-1/#comment-18770</link>
		<dc:creator>ambethia</dc:creator>
		<pubDate>Thu, 17 Sep 2009 20:18:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.engineyard.com/blog/?p=1884#comment-18770</guid>
		<description>I&#039;m having this issue as well </description>
		<content:encoded><![CDATA[<p>I&#039;m having this issue as well</p>
]]></content:encoded>
	</item>
</channel>
</rss>

