rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: Jeremy Kemper <jeremy@bitsweat.net>
To: rack-devel@googlegroups.com
Subject: Re: The best approach to get the latest Rack for Rails 3
Date: Fri, 27 Nov 2009 18:56:55 -0800	[thread overview]
Message-ID: <69a2885c0911271856s3a24739cr74fc83c752614a8d@mail.gmail.com> (raw)
In-Reply-To: <9a320ba70911271523m16ca305eifb77ac708b55ce78@mail.gmail.com>

On Fri, Nov 27, 2009 at 3:23 PM, Joshua Partogi
<joshua.partogi@gmail.com> wrote:
> The latest Rails 3 server.rb needs Rack's Server class, but this is
> not released yet. What would be the best approach to get the latest
> Rack to be used in conjunction with Rails 3?
>
> Any ideas and suggestions?

gem "rack", "1.0.1", :git => "git://github.com/rails/rack.git"

in your Gemfile.

jeremy

      parent reply	other threads:[~2009-11-28  2:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-27 23:23 The best approach to get the latest Rack for Rails 3 Joshua Partogi
2009-11-28  1:33 ` Priidu
2009-11-28  2:56 ` Jeremy Kemper [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-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://groups.google.com/group/rack-devel

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=69a2885c0911271856s3a24739cr74fc83c752614a8d@mail.gmail.com \
    --to=rack-devel@googlegroups.com \
    /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.
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).