unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Hoptoad setup.
Date: Fri, 14 Oct 2011 08:45:04 +0000	[thread overview]
Message-ID: <20111014084504.GA24915@dcvr.yhbt.net> (raw)
In-Reply-To: <CAF-xwzSFsgc1ehuaM71WpqjoQQVy9Axn0aCTRjGnLENh=eHjmw@mail.gmail.com>

Marcin Stecki <madsheeppl@gmail.com> wrote:
> In my ror 3.0.10 app Unicorn somehow causes my application to show
> errors on staging like it was development environment (with backtrace
> and everything) instead of sending them to hoptoad. This is strange -
> same app on mongrel shows custom 500 page and sends errors to hoptoad
> as expected.
> 
> Rails configuration seems to be ok, works on mongrel and passenger.
> To lunch my app i'm using pretty basic command:
> 
> 
> "bundle exec unicorn_rails -c config/unicorn.rb -D -E staging"

I haven't looked at hoptoad before, but does setting RACK_ENV=none
help?

  RACK_ENV=none bundle exec unicorn_rails -c config/unicorn.rb -D -E staging

Or even swapping "unicorn_rails" for plain "unicorn":

  RACK_ENV=none RAILS_ENV=staging bundle exec unicorn -c config/unicorn.rb -D

"unicorn_rails" was mainly designed for Rails 2.2 and earlier,
Rack-capable versions of Rails are probably better served by just
"unicorn"

Maybe others on this list have more experience with this particular
combination, not much of a Rails user myself...
_______________________________________________
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:[~2011-10-14 10:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-14  7:33 Hoptoad setup Marcin Stecki
2011-10-14  8:45 ` Eric Wong [this message]

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=20111014084504.GA24915@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --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).