clogger RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: clogger@librelist.org
Subject: where does clogger go, now?
Date: Thu, 21 Jul 2011 16:55:41 -0700	[thread overview]
Message-ID: <20110721235541.GA18484@dcvr.yhbt.net> (raw)
In-Reply-To: <20110721235541.GA18484@dcvr.yhbt.net>

What's missing?  What could be better?

I think we support all of the nginx variables that can be mapped to
Rack at this point.

I'm hesitant to add server-specific support of any sort since that'd
nudge us back to the pre-Rack days when everybody was writing apps for
specific servers.

So it looks like this project will just sit idle and wait for:

* bug fixes
* nginx changes
* Ruby changes
* Rack changes

Anyways I'm open to suggestions as long as it doesn't include
endorsing non-Free software or any for-profit entities.

-- 
Eric Wong


           reply	other threads:[~2011-07-21 23:55 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20110721235541.GA18484@dcvr.yhbt.net>]

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

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

  git send-email \
    --in-reply-to=20110721235541.GA18484@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=clogger@librelist.org \
    --subject='Re: where does clogger go, now?' \
    /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

Code repositories for project(s) associated with this inbox:

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