From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: using unicorn as a local development server
Date: Thu, 23 Feb 2012 05:19:54 +0000 [thread overview]
Message-ID: <20120223051953.GA31014@dcvr.yhbt.net> (raw)
In-Reply-To: <alpine.OSX.2.00.1202222059210.1173@vincent.local>
"Patrick J. Collins" <patrick@collinatorstudios.com> wrote:
> > You shouldn't even need the logger directive, it goes to stderr by
> > default so your console will still show it.
>
> Hmm that's odd because I noticed as soon as I began using unicorn that I got
> very little output. For example, running my app and browsing to various pages, this is all I see:
<snip>
> None of the development.log output is getting piped into this, so that's why I
> thought doing the Logger.new(STDOUT) would get that behavior to happen just as
> it does with the default rails server.
Odd, not sure what Rails is doing (I don't normally use Rails). It must
be something weird with the way Rails modifies all existing logger
objects (I know it clobbers the default logger formatter somehow
as mentioned in the FAQ). Oh well, I suppose your workaround is as good
as any.
_______________________________________________
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
next prev parent reply other threads:[~2012-02-23 5:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 2:29 using unicorn as a local development server Patrick J. Collins
2012-02-23 4:30 ` Eric Wong
2012-02-23 5:01 ` Patrick J. Collins
2012-02-23 5:19 ` Eric Wong [this message]
2012-02-23 5:49 ` Alex Sharp
2012-02-24 18:47 ` Patrick J. Collins
2012-02-24 19:26 ` Alex Sharp
-- strict thread matches above, loose matches on Subject: below --
2012-02-24 17:43 Matt Smith
2012-02-24 23:10 ` 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=20120223051953.GA31014@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).