<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Is Rails too big?</title>
	<link>http://www.rubyfleebie.com/is-rails-too-big/</link>
	<description>Because programming should be fun</description>
	<pubDate>Mon, 05 Jan 2009 23:57:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.2</generator>

	<item>
		<title>By: Chris B</title>
		<link>http://www.rubyfleebie.com/is-rails-too-big/#comment-36</link>
		<author>Chris B</author>
		<pubDate>Wed, 28 Mar 2007 11:44:43 +0000</pubDate>
		<guid>http://www.rubyfleebie.com/is-rails-too-big/#comment-36</guid>
					<description>I'm not sure Rails itself is too big, it is geared afterall to the creation of full blown web applications as opposed to smaller 'sites' and 'mini-apps' but you're very right (imho) about the deployment agonies, from my experience Rails deployment is the 'maelstrom of hell' we dare not speak about! There was an interesting post by Dr Nic about JRuby and Tomcat, where he laudes their accomplishments. Quote:
“Upload it … and it just works” - I still don’t think I’ve heard of a technical solution for deploying Rails apps that’s been bold enough to claim this.
Article at: (http://drnicwilliams.com/2007/03/23/drop-rails-into-tomcat-and-it-just-works-ola-bini-on-jruby-presentation/)

I dream of the day of being able to upload Rails apps to servers the way we do PHP apps - oh the joy!!

Great blog btw - loving the articles! Keep it up</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure Rails itself is too big, it is geared afterall to the creation of full blown web applications as opposed to smaller &#8217;sites&#8217; and &#8216;mini-apps&#8217; but you&#8217;re very right (imho) about the deployment agonies, from my experience Rails deployment is the &#8216;maelstrom of hell&#8217; we dare not speak about! There was an interesting post by Dr Nic about JRuby and Tomcat, where he laudes their accomplishments. Quote:<br />
“Upload it … and it just works” - I still don’t think I’ve heard of a technical solution for deploying Rails apps that’s been bold enough to claim this.<br />
Article at: (http://drnicwilliams.com/2007/03/23/drop-rails-into-tomcat-and-it-just-works-ola-bini-on-jruby-presentation/)</p>
<p>I dream of the day of being able to upload Rails apps to servers the way we do PHP apps - oh the joy!!</p>
<p>Great blog btw - loving the articles! Keep it up</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Frank</title>
		<link>http://www.rubyfleebie.com/is-rails-too-big/#comment-37</link>
		<author>Frank</author>
		<pubDate>Thu, 29 Mar 2007 19:37:56 +0000</pubDate>
		<guid>http://www.rubyfleebie.com/is-rails-too-big/#comment-37</guid>
					<description>Thanks Chris, glad you like the blog!

I liked how you called "maelstrom of hell" the deployment of rails applications. =) I would tend to agree.

I'm going to have a look at the article you mentioned.</description>
		<content:encoded><![CDATA[<p>Thanks Chris, glad you like the blog!</p>
<p>I liked how you called &#8220;maelstrom of hell&#8221; the deployment of rails applications. =) I would tend to agree.</p>
<p>I&#8217;m going to have a look at the article you mentioned.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Josh</title>
		<link>http://www.rubyfleebie.com/is-rails-too-big/#comment-45</link>
		<author>Josh</author>
		<pubDate>Sat, 31 Mar 2007 01:27:04 +0000</pubDate>
		<guid>http://www.rubyfleebie.com/is-rails-too-big/#comment-45</guid>
					<description>Maybe you should try Camping?

I haven't had the time or gumption to do so myself yet, but it's basically as lightweight as you describe cakePHP, plus it's Ruby.

Also greatly enjoying the blog here.</description>
		<content:encoded><![CDATA[<p>Maybe you should try Camping?</p>
<p>I haven&#8217;t had the time or gumption to do so myself yet, but it&#8217;s basically as lightweight as you describe cakePHP, plus it&#8217;s Ruby.</p>
<p>Also greatly enjoying the blog here.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Russ Brooks</title>
		<link>http://www.rubyfleebie.com/is-rails-too-big/#comment-209</link>
		<author>Russ Brooks</author>
		<pubDate>Thu, 17 May 2007 03:56:49 +0000</pubDate>
		<guid>http://www.rubyfleebie.com/is-rails-too-big/#comment-209</guid>
					<description>I haven't encountered this "Maelstrom of Hell" with Rails deployment.  Perhaps you are referring to deploying to remote hosting providers, where you have no control of the underlying technologies, rather than a self-administrated server.  Nearly **all** hosting providers I've encountered who claim to support Rails do not have their Rails environment configured properly.  They are using Apache or LigHTTPd with FastCGI (no Mongrel cluster).  These are notoriously a slow and unreliable Rails environments.  Apache leaks about 20 MB per day with some Rails apps and Lighty has a long-running bug in the mod_proxy plugin that causes 500 errors.  The fastest and most-reliable Rails environment is using [nginx](http://nginx.net/) as your front-line reverse proxy serving static content with a Mongrel cluster serving your Rails.  Granted, nginx is the new kid on the block and people are just wising up to its speed and reliability, but as time passes, Rails ISP's will implement this setup more and more and you will see that ubiquitous "drag and drop" convenience like we see with PHP today.

Rails deployment for me with this setup couldn't be easier.  I really do "copy the files and they work" -- especially when you use SQLite as your database.  The database resides right in your project so everything is self-contained.  To see the article I wrote documenting the setup of this environment and see the site that is running on it, please check out
[Install nginx and Mongrel Cluster on Kubuntu](http://www2.russbrooks.com:8080/2007/4/21/install-nginx-mongrel-cluster-on-kubuntu)

Hope this helps at least a few people.</description>
		<content:encoded><![CDATA[<p>I haven&#8217;t encountered this &#8220;Maelstrom of Hell&#8221; with Rails deployment.  Perhaps you are referring to deploying to remote hosting providers, where you have no control of the underlying technologies, rather than a self-administrated server.  Nearly **all** hosting providers I&#8217;ve encountered who claim to support Rails do not have their Rails environment configured properly.  They are using Apache or LigHTTPd with FastCGI (no Mongrel cluster).  These are notoriously a slow and unreliable Rails environments.  Apache leaks about 20 MB per day with some Rails apps and Lighty has a long-running bug in the mod_proxy plugin that causes 500 errors.  The fastest and most-reliable Rails environment is using [nginx](http://nginx.net/) as your front-line reverse proxy serving static content with a Mongrel cluster serving your Rails.  Granted, nginx is the new kid on the block and people are just wising up to its speed and reliability, but as time passes, Rails ISP&#8217;s will implement this setup more and more and you will see that ubiquitous &#8220;drag and drop&#8221; convenience like we see with PHP today.</p>
<p>Rails deployment for me with this setup couldn&#8217;t be easier.  I really do &#8220;copy the files and they work&#8221; &#8212; especially when you use SQLite as your database.  The database resides right in your project so everything is self-contained.  To see the article I wrote documenting the setup of this environment and see the site that is running on it, please check out<br />
[Install nginx and Mongrel Cluster on Kubuntu](http://www2.russbrooks.com:8080/2007/4/21/install-nginx-mongrel-cluster-on-kubuntu)</p>
<p>Hope this helps at least a few people.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
