<?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"
	>
<channel>
	<title>Kommentare zu: Plesk und Ruby on Rails</title>
	<atom:link href="http://www.ktb-blog.de/allgemein/plesk-und-ruby-on-rails/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ktb-blog.de/allgemein/plesk-und-ruby-on-rails/</link>
	<description>kill time before time kills you</description>
	<pubDate>Mon, 06 Feb 2012 23:47:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>Von: KTB</title>
		<link>http://www.ktb-blog.de/allgemein/plesk-und-ruby-on-rails/#comment-88</link>
		<dc:creator>KTB</dc:creator>
		<pubDate>Tue, 15 Dec 2009 09:52:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.ktb-blog.de/?p=257#comment-88</guid>
		<description>Kurzes Update: Dieser Weg hat bei mir nur seeeehr bedingt funktioniert. Deshalb bin ich nun einen anderen Weg gegangen, der ausgezeichnet funktioniert. Das Stichwort lautet Phusion Passenger (aka mod_rails). Hiermit kann Rails mit dem Apache2 zwangsverheiratet werden ;)

Hier ein Auszug von modrails.com
------------------------------------------------
Phusion Passenger™ — a.k.a. mod_rails or mod_rack — makes deployment of Ruby web applications, such as those built on the revolutionary Ruby on Rails web framework, a breeze. It follows the usual Ruby on Rails conventions, such as “Don’t-Repeat-Yourself”. 
•Deployment is only a matter of uploading application files. No Ruby (on Rails)-specific server configuration required! 
•Supports both the industry standard Apache web server and the fast and lightweight Nginx web server. 
•Allows Ruby on Rails applications to use about 33% less memory, when used in combination with Ruby Enterprise Edition (optional). 
•Zero maintenance. No port management, server process monitoring or stale file cleanup required. Errors are automatically recovered whenever possible. 
•Designed for performance, stability and security. Phusion Passenger should never crash Apache even in case of crashing Rails applications. 
•Well-documented, for both system administrators and developers!</description>
		<content:encoded><![CDATA[<p>Kurzes Update: Dieser Weg hat bei mir nur seeeehr bedingt funktioniert. Deshalb bin ich nun einen anderen Weg gegangen, der ausgezeichnet funktioniert. Das Stichwort lautet Phusion Passenger (aka mod_rails). Hiermit kann Rails mit dem Apache2 zwangsverheiratet werden <img src='http://www.ktb-blog.de/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>Hier ein Auszug von modrails.com<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<br />
Phusion Passenger™ — a.k.a. mod_rails or mod_rack — makes deployment of Ruby web applications, such as those built on the revolutionary Ruby on Rails web framework, a breeze. It follows the usual Ruby on Rails conventions, such as “Don’t-Repeat-Yourself”.<br />
•Deployment is only a matter of uploading application files. No Ruby (on Rails)-specific server configuration required!<br />
•Supports both the industry standard Apache web server and the fast and lightweight Nginx web server.<br />
•Allows Ruby on Rails applications to use about 33% less memory, when used in combination with Ruby Enterprise Edition (optional).<br />
•Zero maintenance. No port management, server process monitoring or stale file cleanup required. Errors are automatically recovered whenever possible.<br />
•Designed for performance, stability and security. Phusion Passenger should never crash Apache even in case of crashing Rails applications.<br />
•Well-documented, for both system administrators and developers!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

