rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: James Tucker <jftucker@gmail.com>
To: rack-devel@googlegroups.com
Subject: Re: [PATCH] README: update to add yahns to the list of servers
Date: Mon, 14 Jul 2014 20:56:53 -0700	[thread overview]
Message-ID: <CABGa_T-3psUfUsZEz9Pj4DWo6F0dxz4r0x4HVH+-bo5qtcSGvw@mail.gmail.com> (raw)
In-Reply-To: <20131018195222.GA22200@dcvr.yhbt.net>

[-- Attachment #1: Type: text/plain, Size: 2152 bytes --]

accepted, thanks!


On Fri, Oct 18, 2013 at 12:52 PM, Eric Wong <normalperson@yhbt.net> wrote:

> yahns will eventually support more than Rack, but for now
> it only knows Rack.
>
> ref: http://yahns.yhbt.net/README
> ---
>   Fwiw, yahns has reasonable defaults, so maybe a builtin Rack handler
>   is in order.  But I'm not sure if Rack is adding support for more
>   server handlers (and I'm not sure if it's beneficial to have two
>   ways to configure yahns...)
>
>   If you prefer: git pull git://git.bogomips.org/rack.git yahns
>
>   The following changes since commit
> 1f47a4478546602d3c17902cc3faf42b106f0638:
>
>     Merge pull request #606 from aweiksnar/patch-1 (2013-09-27 01:35:33
> -0700)
>
>   are available in the git repository at:
>
>     git://git.bogomips.org/rack.git yahns
>
>   for you to fetch changes up to a8b6b005b1635cd4e4880021fdf00e7d07dd713c:
>
>     README: update to add yahns to the list of servers (2013-10-18
> 19:46:12 +0000)
>
>   ----------------------------------------------------------------
>   Eric Wong (1):
>         README: update to add yahns to the list of servers
>
>  README.rdoc | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/README.rdoc b/README.rdoc
> index 7a3c8d5..912fe5f 100644
> --- a/README.rdoc
> +++ b/README.rdoc
> @@ -33,6 +33,7 @@ These web servers include Rack handlers in their
> distributions:
>  * Unicorn
>  * unixrack
>  * uWSGI
> +* yahns
>  * Zbatery
>
>  Any valid Rack app will run the same on all these handlers, without
> --
> 1.8.4.483.g7fe67e6.dirty
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Rack Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rack-devel+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups "Rack Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rack-devel+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 3209 bytes --]

  reply	other threads:[~2014-07-15  3:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18 19:52 [PATCH] README: update to add yahns to the list of servers Eric Wong
2014-07-15  3:56 ` James Tucker [this message]
2014-07-15 21:24   ` Eric Wong
2014-07-17 21:17     ` James Tucker
2014-08-04  9:08       ` [PATCH] README: remove Rainbows! and Zbatery from server list Eric Wong
2015-03-01 10:19         ` Eric Wong
2015-03-01 14:37           ` Santiago Pastorino

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=CABGa_T-3psUfUsZEz9Pj4DWo6F0dxz4r0x4HVH+-bo5qtcSGvw@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).