From: "Patrick J. Collins" <patrick@collinatorstudios.com>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: using unicorn as a local development server
Date: Wed, 22 Feb 2012 21:01:25 -0800 (PST) [thread overview]
Message-ID: <alpine.OSX.2.00.1202222059210.1173@vincent.local> (raw)
In-Reply-To: <20120223043007.GA20356@dcvr.yhbt.net>
> 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:
I, [2012-02-22T19:38:30.511485 #8933] INFO -- : listening on addr=0.0.0.0:3000 fd=3
I, [2012-02-22T19:38:30.511938 #8933] INFO -- : worker=0 spawning...
I, [2012-02-22T19:38:30.514042 #8933] INFO -- : master process ready
I, [2012-02-22T19:38:30.515943 #8934] INFO -- : worker=0 spawned pid=8934
I, [2012-02-22T19:38:30.516671 #8934] INFO -- : Refreshing Gem list
DEPRECATION WARNING: Calling set_table_name is deprecated. Please use `self.table_name = 'the_name'` instead. (called from require at /Users/patrick/.rvm/gems/ruby-1.9.2-p290@global/gems/bundler-1.1.rc.7/lib/bundler/runtime.rb:68)
I, [2012-02-22T19:38:56.879509 #8934] INFO -- : worker=0 ready
I, [2012-02-22T19:49:22.737427 #8933] INFO -- : SIGWINCH ignored because we're not daemonized
I, [2012-02-22T19:49:35.800600 #8933] INFO -- : SIGWINCH ignored because we're not daemonized
I, [2012-02-22T20:02:05.792427 #8933] INFO -- : SIGWINCH ignored because we're not daemonized
I, [2012-02-22T20:03:07.315092 #8933] INFO -- : SIGWINCH ignored because we're not daemonized
I, [2012-02-22T20:03:36.330349 #8933] INFO -- : SIGWINCH ignored because we're not daemonized
I, [2012-02-22T20:04:33.278243 #8933] INFO -- : SIGWINCH ignored because we're not daemonized
I, [2012-02-22T20:05:33.188828 #8933] INFO -- : SIGWINCH ignored because we're not daemonized
...
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.
Patrick J. Collins
http://collinatorstudios.com
_______________________________________________
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:11 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 [this message]
2012-02-23 5:19 ` Eric Wong
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=alpine.OSX.2.00.1202222059210.1173@vincent.local \
--to=patrick@collinatorstudios.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).