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: Working directory and config.ru
Date: Wed, 9 Jun 2010 11:04:31 -0700	[thread overview]
Message-ID: <20100609180431.GA8027@dcvr.yhbt.net> (raw)
In-Reply-To: <AANLkTimKb7JARr_69nfVrJLvMZH3Gvs1o_KwZFLKfuxy@mail.gmail.com>

Pierre Baillet <oct@fotonauts.com> wrote:
> Hi,
> I naively expected unicorn to honor the working_directory
> configuration directive before attempting to locate the config.ru but
> this does not seem to be the case. Is this behavior wanted ? From the
> code, I can guess that the configuration file parsing is done much
> later  than the current config.ru location attempt.

Hi Pierre,

Oops, definitely not wanted behavior.  Unicorn should honor
working_directory with regard to config.ru.  I'll start working
on a fix shortly, thanks for the report!

Eric Wong
Unicorn mailing list - mongrel-unicorn@rubyforge.org
Do not quote signatures (like this one) or top post when replying

  reply	other threads:[~2010-06-09 18:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09 12:58 Working directory and config.ru Pierre Baillet
2010-06-09 18:04 ` Eric Wong [this message]
2010-06-10  9:58   ` 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:

  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=20100609180431.GA8027@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=mongrel-unicorn@rubyforge.org \


* 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


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).