Pavel -- thanks again for all your work!

Also, on a sidenote -- we were running passenger
2.2.5 before we went ahead and upgraded to 2.2.10.

If you are running 2.2.5 you'll need to edit
/usr/lib/ruby/gems/1.8/gems/passenger-2.2.5/lib/phusion_passenger/utils.rb
and tack on a

require 'stringio'

as for whatever reason that was not there and is needed

or you can just go ahead and upgrade to 2.2.10 as it is present there.

-ian

On 16:53 Mon 22 Feb     , Pavel Kunc wrote:
> Thanks a lot Ian. I'm glad that 1.1.0.pre works for you now.
> 
> I'd like to transform this to the wiki at some point :-)
> 
> Pavel
> 
> On Feb 22, 6:59 pm, Ian Eyberg <[email protected]> wrote:
> > hi all,
> >
> >   just got production up to 1.1.0.pre w/bundler 0.9.7
> > at merboutpost's request I'm relaying what all needed to
> > be done
> >
> > pretty sure this upgrade came from 1.0.x that was dled
> > from the repos on github -- the new stuff of course
> > comes from gemcutter; we had a Gemfile but weren't using
> > it yet as it was not necessary yet
> >
> > 1) rm all your merb gems.
> >
> > 2) make sure you have jeweler and gem 1.3.6
> >   sudo gem update --system
> >   sudo gem install jeweler --no-ri --no-rdoc
> >
> > 3) install new merb
> >   sudo gem install merb --pre --no-ri --no-rdoc
> >
> > 4) copy all your stuff in config/depedencies.rb
> >   to Gemfile -- some gems that have diff. class
> >   names rather than their gem names need that
> >   require_as which in Gemfile format is now
> >   'require'
> >
> >   for instance
> >
> >   gem "antage-merb-recaptcha",    "1.0.3", :require => "merb-recaptcha"
> >
> > 5) if you are using haml like we are make sure that
> >   both haml and merb-haml are included in your Gemfile;
> >   got caught up on that for a second
> >
> > 6) make sure your config.ru is setup to use the bundler
> > stuff -- I more or less copied mine from the wiki --
> > the only thing that I ended up forcing was the production
> > env -- not quite sure why it was taking it
> >
> > begin
> >   require ::File.expand_path('.bundle/environment', __FILE__)
> > rescue LoadError
> >   require 'rubygems'
> >   require 'bundler'
> >   Bundler.setup
> > end
> >
> > require 'merb-core'
> > Merb::Config.setup(:merb_root   => 
> > ::File.expand_path(::File.dirname(__FILE__)),
> >                    :environment => "production") #ENV['RACK_ENV'])
> > Merb.environment = "production"
> > Merb.root = Merb::Config[:merb_root]
> > Merb::BootLoader.run
> >
> > # use PathPrefix Middleware if :path_prefix is set in Merb::Config
> > if prefix = ::Merb::Config[:path_prefix]
> >   use Merb::Rack::PathPrefix, prefix
> > end
> >
> > # comment this out if you are running merb behind a load balancer
> > # that serves static files
> > use Merb::Rack::Static, Merb.dir_for(:public)
> >
> > run Merb::Rack::Application.new
> >
> > # broken pipe fixx???
> > #
> > # require 'fileutils'
> > # FileUtils.rm_r Dir.glob('/tmp/ruby_inline*')
> > # temp = Tempfile.new('ruby_inline', '/tmp')
> > # dir = temp.path
> > # temp.delete
> > # Dir.mkdir(dir, 0755)
> > # ENV['INLINEDIR'] = dir
> >
> > this last little bit that is commented out was a hack-fix
> > for something that used to trip up passenger -- doesn't seem
> > that I need it anymore
> >
> > if you don't have your config.ru setup right it'll probably
> > complain about missing some gems or something to that effect
> >
> > tail -f /var/log/apache2/error.log
> > tail -f log/production.log are your friends
> >
> >   -- running it under thin or mongrel by itself will not tell
> > you anything since it will find the gems fine
> >
> > thanks to everyone on #merb that helped out -- this is always
> > not such a fun time -- I wish I could follow and help out
> > with merb development as I bitch about it enough ;) -- it's
> > just that our pivotal story list seems to be the limit as
> > x approaches wtf
> >
> > anyways cheers,
> >
> > -ian
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "merb" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group at 
> http://groups.google.com/group/merb?hl=en.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"merb" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected].
For more options, visit this group at http://groups.google.com/group/merb?hl=en.

Reply via email to