From: "Jérémy Lecour" <jeremy.lecour@gmail.com>
To: Eric Wong <e@80x24.org>
Cc: Pirate Praveen <praveen@debian.org>, unicorn-public@bogomips.org
Subject: Re: Request to follow SemVer/mention it in homepage
Date: Tue, 29 Sep 2015 11:26:27 +0200 [thread overview]
Message-ID: <CANrRGgpX9F8fc_mkvqphZWR8BX9LsR9WbiMzmjJbANLA3PULVg@mail.gmail.com> (raw)
In-Reply-To: <20150929073650.GA7434@dcvr.yhbt.net>
On Tue, Sep 29, 2015 at 9:36 AM, Eric Wong <e@80x24.org> wrote:
> Tying a Rack app to unicorn is totally, completely wrong and defeats the
> point of Rack.
I completely agree with that statement.
However, having an app with hard dependency on a specific app server
is not the same a providing a default setup for a given app server.
For example, an app like Gitlab, Discourse or whatever might provide a
default good configuration for Unicorn, a set of optimisations in the
context of a Unicorn (pre/post fork instructions…) and have something
that works great out of the box, even if it's not restricted to
Unicorn.
Someone who would want to change to Passenger, Puma or else would have
to adapt the configuration and port the optimizations, but the app
would work the same as with Unicorn, without crippled features.
Someone who wouldn't change or tweak anything would have a good
setting by default.
--
Jérémy Lecour :
http://jeremy.wordpress.com - http://twitter.com/jlecour
next prev parent reply other threads:[~2015-09-29 9:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 6:38 Request to follow SemVer/mention it in homepage Pirate Praveen
2015-09-29 7:36 ` Eric Wong
2015-09-29 7:46 ` Lin Jen-Shin (godfat)
2015-09-29 8:00 ` Pirate Praveen
2015-09-29 19:36 ` Eric Wong
2015-09-30 16:04 ` Pirate Praveen
2015-09-30 19:51 ` Eric Wong
2015-10-01 4:56 ` Pirate Praveen
2015-10-01 11:18 ` Pirate Praveen
2015-10-01 19:06 ` Eric Wong
2015-09-29 9:26 ` Jérémy Lecour [this message]
2015-09-29 19:43 ` 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=CANrRGgpX9F8fc_mkvqphZWR8BX9LsR9WbiMzmjJbANLA3PULVg@mail.gmail.com \
--to=jeremy.lecour@gmail.com \
--cc=e@80x24.org \
--cc=praveen@debian.org \
--cc=unicorn-public@bogomips.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).