<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://wiki.merbivore.com/lib/exe/css.php?s=feed" type="text/css"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Merb Wiki deployment</title>
    <subtitle></subtitle>
    <link rel="alternate" type="text/html" href="http://wiki.merbivore.com/"/>
    <id>http://wiki.merbivore.com/</id>
    <updated>2010-08-19T15:27:27-07:00</updated>
    <generator>FeedCreator 1.7.2-ppt DokuWiki</generator>
<link rel="self" type="application/atom+xml" href="http://wiki.merbivore.com/feed.php" />
    <entry>
        <title>Bundling your app with merb.thor</title>
        <link rel="alternate" type="text/html" href="http://wiki.merbivore.com/deployment/bundling?rev=1281725124&amp;do=diff"/>
        <published>2010-08-13T11:45:24-07:00</published>
        <updated>2010-08-13T11:45:24-07:00</updated>
        <id>http://wiki.merbivore.com/deployment/bundling?rev=1281725124&amp;do=diff</id>
        <summary>Why bundling


While you are developing on your machine, your application might be running smoothly.
Your application relies on multiple libraries/Ruby gems already installed on your machine.
While everything might work now, the same gems probably won't be available on the server you will deploy to. If you work with other developers, they might be missing dependencies or have different versions. You might also start a new project and use install a newer version of some libraries which might crea…</summary>
    </entry>
    <entry>
        <title>Deploying a Merb application</title>
        <link rel="alternate" type="text/html" href="http://wiki.merbivore.com/deployment/deploying?rev=1225467270&amp;do=diff"/>
        <published>2008-10-31T08:34:30-07:00</published>
        <updated>2008-10-31T08:34:30-07:00</updated>
        <id>http://wiki.merbivore.com/deployment/deploying?rev=1225467270&amp;do=diff</id>
        <summary>Watch Lindsay's deployment talk from MerbCamp.

Capistrano Task


Matt Aimonetti has a good writeup and example cap file on his blog. 


Zack Chandler has a another writeup which includes an example cap file on his blog.</summary>
    </entry>
    <entry>
        <title>Deploying your app with HAProxy</title>
        <link rel="alternate" type="text/html" href="http://wiki.merbivore.com/deployment/haproxy?rev=1229799492&amp;do=diff"/>
        <published>2008-12-20T10:58:12-07:00</published>
        <updated>2008-12-20T10:58:12-07:00</updated>
        <id>http://wiki.merbivore.com/deployment/haproxy?rev=1229799492&amp;do=diff</id>
        <summary># this is our main merb application
merb =  Merb::Rack::Application.new

hapong = lambda do |env|
  if env[&quot;REQUEST_METHOD&quot;] == &quot;OPTIONS&quot; &amp;&amp; env[&quot;REQUEST_URI&quot;] == &quot;/&quot;
    [200, {}, &quot;PONG!\n&quot;]
  else
    [404, {}, &quot;No PONG! here, move along&quot;]
  end
end

run Rack::Cascade.new([hapong, merb])</summary>
    </entry>
    <entry>
        <title>Deploying with Passenger</title>
        <link rel="alternate" type="text/html" href="http://wiki.merbivore.com/deployment/passenger?rev=1237570823&amp;do=diff"/>
        <published>2009-03-20T10:40:23-07:00</published>
        <updated>2009-03-20T10:40:23-07:00</updated>
        <id>http://wiki.merbivore.com/deployment/passenger?rev=1237570823&amp;do=diff</id>
        <summary>As of version 2.0, Phusion Passenger supports Rack (and thus Merb) through a Rack  config.ru file placed at the root of an app:

# config.ru
require 'rubygems'

# Uncomment if your app uses bundled gems
#gems_dir = File.expand_path(File.join(File.dirname(__FILE__), 'gems'))
#Gem.clear_paths
#$BUNDLE = true
#Gem.path.unshift(gems_dir)

require 'merb-core'

Merb::Config.setup(:merb_root   =&gt; File.expand_path(File.dirname(__FILE__)),
                   :environment =&gt; ENV['RACK_ENV'])
Merb.environm…</summary>
    </entry>
</feed>
