unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: debian-ruby@lists.debian.org
Cc: Rahulkrishnan R A <rahulkrishnanfs@gmail.com>,
	Hleb Valoshka <375gnu@gmail.com>,
	Christian Hofstaedtler <zeha@debian.org>,
Subject: Re: RFS: unicorn
Date: Fri, 12 Feb 2016 21:34:11 +0000	[thread overview]
Message-ID: <20160212213411.GA13868@dcvr.yhbt.net> (raw)
In-Reply-To: <20160212183137.GA15177@percival.namespace.at>

Christian Hofstaedtler <zeha@debian.org> wrote:
> Hleb,
> * Rahulkrishnan R A <rahulkrishnanfs@gmail.com> [160212 16:52]:
> > I have updated unicorn to the latest version. It is lintian clean and
> > tested with pbuilder. Further information about this package can be
> > accessed from the URL  :
> > *https://anonscm.debian.org/cgit/pkg-ruby-extras/unicorn.git
> I'd value your feedback on this.

(upstream chiming in, too; +Cc unicorn-public@bogomips.org :)

Can you take a look at updating the debian/unicorn.service to be
based on the examples/unicorn@.service and examples/unicorn.socket
files in v5.0.1 upstream?

I'm no systemd expert, but the @.service file allowing multiple
instances makes more sense to me since USR2 upgrades won't work
well under systemd.

And of course socket activation rocks :>


       reply	other threads:[~2016-02-12 21:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJfKhMSyhNgijOeaZ3zA4g7d_0vR7ePKMDRGvUWy4n3K4Bem9A@mail.gmail.com>
     [not found] ` <20160212183137.GA15177@percival.namespace.at>
2016-02-12 21:34   ` Eric Wong [this message]
2016-02-14  5:52     ` RFS: unicorn Pirate Praveen

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:

  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=20160212213411.GA13868@dcvr.yhbt.net \
    --to=e@80x24.org \
    --cc=375gnu@gmail.com \
    --cc=debian-ruby@lists.debian.org \
    --cc=rahulkrishnanfs@gmail.com \
    --cc=unicorn-public@bogomips.org \
    --cc=zeha@debian.org \


* 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


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