From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Unicorn logging in production env
Date: Tue, 16 Aug 2011 17:45:03 -0700 [thread overview]
Message-ID: <20110817004503.GA2793@dcvr.yhbt.net> (raw)
In-Reply-To: <6010D71F-43CE-4D71-82C5-3C2AB2FD897B@adobe.com>
John Fieber <jfieber@adobe.com> wrote:
> On Aug 16, 2011, at 8:45 AM, Serg Podtynnyi wrote:
> > Hi All, as I can see on
> > https://github.com/defunkt/unicorn/blob/master/lib/unicorn.rb#L53
> > the Rack::CommonLogger used only in development env and in weird evn
> > called "deployment".
> > Any chance to add "production" to this case?
>
> My wish would be to remove all of the magically added middlewares.
> Leave the middleware assembly to config.ru.
If you can convince Rack upstream, Unicorn will follow. I dislike
magic middlewares, too, but I try to follow Rack to minimize the
differences for people using unicorn (and also switching between
"rackup" and unicorn).
> Failing that, my next wish would be to have the magic opt-in. Failing
> that, my next wish would be for an easy opt-out. It is maddening to
> debug an error in your app that causes the ShowExceptions middleware
> to crash, masking your actual problem.
I always set RACK_ENV=none for any services I run so nothing
gets added automatically.
--
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
prev parent reply other threads:[~2011-08-17 1:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 15:45 Unicorn logging in production env Serg Podtynnyi
2011-08-16 17:30 ` Eric Wong
2011-08-17 9:21 ` Serg Podtynnyi
2011-08-17 9:58 ` Eric Wong
2011-08-17 10:04 ` Eric Wong
2011-08-16 22:17 ` John Fieber
2011-08-17 0: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=20110817004503.GA2793@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).