I''m running unicorn and unicorn-rails 0.96.1 and the latest Rails 3 beta gem. ?Firing up unicorn_rails spews "RAILS_ENV not defined by config/boot". ?I know this is likely a result of RAILS_ROOT being deprecated?in Rails 3 but I can''t seem to config my way around it. I''m sure other people must have run into this before. ?Is there a quick fix? Thanks
John Wulff <johnwulff at gmail.com> wrote:> I''m running unicorn and unicorn-rails 0.96.1 and the latest Rails 3 > beta gem. ?Firing up unicorn_rails spews "RAILS_ENV not defined by > config/boot". ?I know this is likely a result of RAILS_ROOT being > deprecated?in Rails 3 but I can''t seem to config my way around it. > I''m sure other people must have run into this before. ?Is there a > quick fix?Hi John, I haven''t had a chance to look at Rails 3 yet, but you can probably try just using a plain config.ru with "unicorn" (not "unicorn_rails") ------------------- config.ru ------------------ ENV["RAILS_ENV"] ||= ENV["RACK_ENV"] require "config/environment" use Rails::Rack::Static run ActionController::Dispatcher.new ------------------------------------------------ Let us know how it goes, thanks! -- Eric Wong
John-Paul Bader
2010-Feb-18 19:13 UTC
Rails 3 "RAILS_ENV not defined by config/boot" error
Hey guys, actually I was running my new blog on rails3 and unicorn. I wanted to post about it here but didn''t have the time yet. Indeed you just need unicorn - not unicorn rails. It seems to run all really well - I just need to modify my rc script a bit. Kind regards, John On 18.02.2010, at 20:08, Eric Wong wrote:> John Wulff <johnwulff at gmail.com> wrote: >> I''m running unicorn and unicorn-rails 0.96.1 and the latest Rails 3 >> beta gem. Firing up unicorn_rails spews "RAILS_ENV not defined by >> config/boot". I know this is likely a result of RAILS_ROOT being >> deprecated in Rails 3 but I can''t seem to config my way around it. >> I''m sure other people must have run into this before. Is there a >> quick fix? > > Hi John, > > I haven''t had a chance to look at Rails 3 yet, but you can probably try > just using a plain config.ru with "unicorn" (not "unicorn_rails") > > ------------------- config.ru ------------------ > ENV["RAILS_ENV"] ||= ENV["RACK_ENV"] > require "config/environment" > use Rails::Rack::Static > run ActionController::Dispatcher.new > ------------------------------------------------ > > Let us know how it goes, thanks! > > -- > Eric Wong > _______________________________________________ > Unicorn mailing list - mongrel-unicorn at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-unicorn > Do not quote signatures (like this one) or top post when replying >
Fantastic! Thanks On Thu, Feb 18, 2010 at 11:13 AM, John-Paul Bader <hukl at h3q.com> wrote:> Hey guys, > > actually I was running my new blog on rails3 and unicorn. I wanted to post about it here but didn''t have the time yet. Indeed you just need unicorn - not unicorn rails. It seems to run all really well - I just need to modify my rc script a bit. > > Kind regards, John > > On 18.02.2010, at 20:08, Eric Wong wrote: > >> John Wulff <johnwulff at gmail.com> wrote: >>> I''m running unicorn and unicorn-rails 0.96.1 and the latest Rails 3 >>> beta gem. ?Firing up unicorn_rails spews "RAILS_ENV not defined by >>> config/boot". ?I know this is likely a result of RAILS_ROOT being >>> deprecated in Rails 3 but I can''t seem to config my way around it. >>> I''m sure other people must have run into this before. ?Is there a >>> quick fix? >> >> Hi John, >> >> I haven''t had a chance to look at Rails 3 yet, but you can probably try >> just using a plain config.ru with "unicorn" (not "unicorn_rails") >> >> ------------------- config.ru ------------------ >> ENV["RAILS_ENV"] ||= ENV["RACK_ENV"] >> require "config/environment" >> use Rails::Rack::Static >> run ActionController::Dispatcher.new >> ------------------------------------------------ >> >> Let us know how it goes, thanks! >> >> -- >> Eric Wong >> _______________________________________________ >> Unicorn mailing list - mongrel-unicorn at rubyforge.org >> http://rubyforge.org/mailman/listinfo/mongrel-unicorn >> Do not quote signatures (like this one) or top post when replying >> > > _______________________________________________ > Unicorn mailing list - mongrel-unicorn at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-unicorn > Do not quote signatures (like this one) or top post when replying >
Eric Wong <normalperson at yhbt.net> wrote:> John Wulff <johnwulff at gmail.com> wrote: > > I''m running unicorn and unicorn-rails 0.96.1 and the latest Rails 3 > > beta gem. ?Firing up unicorn_rails spews "RAILS_ENV not defined by > > config/boot". ?I know this is likely a result of RAILS_ROOT being > > deprecated?in Rails 3 but I can''t seem to config my way around it. > > I''m sure other people must have run into this before. ?Is there a > > quick fix? > > Hi John, > > I haven''t had a chance to look at Rails 3 yet, but you can probably try > just using a plain config.ru with "unicorn" (not "unicorn_rails")I''ve been planning on some large-ish changes in Unicorn 0.97.x to bin/{unicorn,unicorn_rails} to make maintenance easier and fix a few minor issues with the existing code. Would the following change be enough to work with Rails 3 out-of-the-box? diff --git a/bin/unicorn_rails b/bin/unicorn_rails index b1458fc..4441c34 100755 --- a/bin/unicorn_rails +++ b/bin/unicorn_rails @@ -128,8 +128,6 @@ app = lambda do || rescue LoadError => err abort "#$0 must be run inside RAILS_ROOT: #{err.inspect}" end - defined?(::RAILS_ROOT) or abort "RAILS_ROOT not defined by config/boot" - defined?(::RAILS_ENV) or abort "RAILS_ENV not defined by config/boot" defined?(::Rails::VERSION::STRING) or abort "Rails::VERSION::STRING not defined by config/boot" (I''ll remember to test when I fix a few other things elsewhere) -- Eric Wong
Apparently Analagous Threads
- Rack content-length Rack::Lint::LintErrors errors with unicorn
- Fwd: Issue starting unicorn with non-ActiveRecord Rails app
- [PATCH] explicitly use escaped minus in man pages
- unicorn doesn't restart properly after cap deploy (not using Bundler)
- unicorn 4.6.0pre1 - hijacking support!