unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: John Wulff <johnw@orcasnet.com>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Rails 3 "RAILS_ENV not defined by config/boot" error
Date: Thu, 18 Feb 2010 11:26:19 -0800	[thread overview]
Message-ID: <d13d1e941002181126ia9eadc0lb6ddd4960b4274f5@mail.gmail.com> (raw)
In-Reply-To: <DABBBFA0-A06E-4D2D-9043-9EA9F3695A77@h3q.com>

Fantastic!  Thanks

On Thu, Feb 18, 2010 at 11:13 AM, John-Paul Bader <hukl@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@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@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@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@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying


  reply	other threads:[~2010-02-18 19:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 18:01 Rails 3 "RAILS_ENV not defined by config/boot" error John Wulff
2010-02-18 19:08 ` Eric Wong
2010-02-18 19:13   ` John-Paul Bader
2010-02-18 19:26     ` John Wulff [this message]
2010-02-18 23:36   ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d13d1e941002181126ia9eadc0lb6ddd4960b4274f5@mail.gmail.com \
    --to=johnw@orcasnet.com \
    --cc=mongrel-unicorn@rubyforge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/unicorn.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).