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: Unicorn and home_run
Date: Wed, 25 Aug 2010 00:50:56 -0700	[thread overview]
Message-ID: <20100825075056.GA14658@dcvr.yhbt.net> (raw)
In-Reply-To: <AANLkTin5V8NOOTecaj2FNAw9H89Rr7Ab3-VtjNx+PZkH@mail.gmail.com>

Jeremy Evans <jeremyevans0@gmail.com> wrote:
> > Are you starting it with "home_run unicorn_rails" or did you install
> > it system-wide?
> 
> Clifton told me that was working for him.  One of the reasons it may
> work where the other way didn't is that in addition to setting up the
> load path, it also requires the library up front.

Yeah, I figured using the "home_run" wrapper would be less than
ideal since it would get lost during exec upgrades and newer
versions of home_run wouldn't get picked up the same way it'd get
picked up in a system install.

> I think this problem is solved in the master branch.

Thanks.  I'd be eager to hear how it works out since this could be a
popular library very soon :) Is there a home_run mailing list I could
follow?

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


  reply	other threads:[~2010-08-25  7:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.96.1282670516.23553.mongrel-unicorn@rubyforge.org>
     [not found] ` <AANLkTingOCVVTyCDbA8RC=Vf7LV=HyCMhtqcJ4RLg9Xy@mail.gmail.com>
2010-08-24 19:58   ` Unicorn and home_run Eric Wong
2010-08-24 20:39     ` Clifton King
2010-08-24 21:38     ` Jeremy Evans
2010-08-25  7:50       ` Eric Wong [this message]
2010-08-25 14:46         ` Jeremy Evans
2010-08-26  4:33           ` 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=20100825075056.GA14658@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).