<?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: rubyworks-ec2 0.1.3</title>
	<atom:link href="http://nutrun.com/weblog/rubyworks-ec2-013/feed/" rel="self" type="application/rss+xml" />
	<link>http://nutrun.com/weblog/rubyworks-ec2-013/</link>
	<description>nutrun</description>
	<lastBuildDate>Mon, 28 Jun 2010 07:35:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: George Malamidis</title>
		<link>http://nutrun.com/weblog/rubyworks-ec2-013/comment-page-1/#comment-315</link>
		<dc:creator>George Malamidis</dc:creator>
		<pubDate>Sat, 12 Jan 2008 02:43:29 +0000</pubDate>
		<guid isPermaLink="false">http://new-site.nutrun.com/?p=115#comment-315</guid>
		<description>Ram,

I haven&#039;t tried the gem with L or XL instances, but I don&#039;t see why it would make a difference.

Try &quot;ec2run ami-30f11459 --instance-type m1.xlarge -k &lt;keypair&gt;&quot;, get the instance id once the instance starts and then do &quot;cap instance:bootstrap&quot;...

You will have to remotely connect to the instance to change the number of mongrels.

&quot;cap instace:ssh&quot;

Monit and Mongrel configurations can be found in &quot;/etc/rails&quot;. SV configs for Mongrels are in &quot;/var/service&quot;

Once you&#039;re happy with your configuration, invoke &quot;cap mongrel stop&quot;, &quot;cap monit:restart&quot; and &quot;cap mongrel:start&quot; from your application&#039;s capified directory.

&quot;cap monit status&quot; will display some useful info on the Mongrel instances.</description>
		<content:encoded><![CDATA[<p>Ram,</p>
<p>I haven&#8217;t tried the gem with L or XL instances, but I don&#8217;t see why it would make a difference.</p>
<p>Try &#8220;ec2run ami-30f11459 &#8211;instance-type m1.xlarge -k &#38;lt;keypair&#38;gt;&#8221;, get the instance id once the instance starts and then do &#8220;cap instance:bootstrap&#8221;&#8230;</p>
<p>You will have to remotely connect to the instance to change the number of mongrels.</p>
<p>&#8220;cap instace:ssh&#8221;</p>
<p>Monit and Mongrel configurations can be found in &#8220;/etc/rails&#8221;. SV configs for Mongrels are in &#8220;/var/service&#8221;</p>
<p>Once you&#8217;re happy with your configuration, invoke &#8220;cap mongrel stop&#8221;, &#8220;cap monit:restart&#8221; and &#8220;cap mongrel:start&#8221; from your application&#8217;s capified directory.</p>
<p>&#8220;cap monit status&#8221; will display some useful info on the Mongrel instances.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ram</title>
		<link>http://nutrun.com/weblog/rubyworks-ec2-013/comment-page-1/#comment-314</link>
		<dc:creator>Ram</dc:creator>
		<pubDate>Mon, 07 Jan 2008 14:04:39 +0000</pubDate>
		<guid isPermaLink="false">http://new-site.nutrun.com/?p=115#comment-314</guid>
		<description>Hey,

Thanks for this gem.

Does this support the &quot;large&quot; and the &quot;extra large&quot; instance in amazon?

Also,how can we change the number of mongrel instances?

Any other tuning that you think would be useful?

Thanks,</description>
		<content:encoded><![CDATA[<p>Hey,</p>
<p>Thanks for this gem.</p>
<p>Does this support the &#8220;large&#8221; and the &#8220;extra large&#8221; instance in amazon?</p>
<p>Also,how can we change the number of mongrel instances?</p>
<p>Any other tuning that you think would be useful?</p>
<p>Thanks,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Malamidis</title>
		<link>http://nutrun.com/weblog/rubyworks-ec2-013/comment-page-1/#comment-313</link>
		<dc:creator>George Malamidis</dc:creator>
		<pubDate>Fri, 14 Dec 2007 19:23:50 +0000</pubDate>
		<guid isPermaLink="false">http://new-site.nutrun.com/?p=115#comment-313</guid>
		<description>Thomas,

At the moment, S3 seems to be the right tool for the job when it comes to backing up and restoring the database. SimpleDB definitely looks like something worth investigating, but I&#039;m not sure whether it&#039;s more appropriate than S3 for something as simple as database back ups.</description>
		<content:encoded><![CDATA[<p>Thomas,</p>
<p>At the moment, S3 seems to be the right tool for the job when it comes to backing up and restoring the database. SimpleDB definitely looks like something worth investigating, but I&#8217;m not sure whether it&#8217;s more appropriate than S3 for something as simple as database back ups.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ThomasB</title>
		<link>http://nutrun.com/weblog/rubyworks-ec2-013/comment-page-1/#comment-312</link>
		<dc:creator>ThomasB</dc:creator>
		<pubDate>Fri, 14 Dec 2007 13:49:24 +0000</pubDate>
		<guid isPermaLink="false">http://new-site.nutrun.com/?p=115#comment-312</guid>
		<description>Amazon SimpleDB was announced today. Is this a natural replacement for the S3 backup of the mysql db in rubyworks-ec2 ? Or do you see SimpleDB as something that every developer must implement in their rails apps as seen fit instead ?</description>
		<content:encoded><![CDATA[<p>Amazon SimpleDB was announced today. Is this a natural replacement for the S3 backup of the mysql db in rubyworks-ec2 ? Or do you see SimpleDB as something that every developer must implement in their rails apps as seen fit instead ?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
