yahns Ruby server user/dev discussion
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: ruby-talk@ruby-lang.org, yahns-public@yhbt.net
Subject: [ANN] yahns 1.16.0 -_- sleepy app server for Ruby
Date: Mon, 6 Aug 2018 01:32:10 +0000	[thread overview]
Message-ID: <20180806013210.GA27913@dcvr> (raw)

A Free Software, multi-threaded, non-blocking network
application server designed for low _idle_ power consumption.
It is primarily optimized for applications with occasional users
which see little or no traffic.  yahns currently hosts Rack/HTTP
applications, but may eventually support other application
types.  Unlike some existing servers, yahns is extremely
sensitive to fatal bugs in the applications it hosts.

* git clone https://yhbt.net/yahns.git
* https://yhbt.net/yahns/README
* https://yhbt.net/yahns/NEWS.atom.xml (supported by most "RSS" readers)
* we only accept plain-text email yahns-public@yhbt.net
* and archive all the mail we receive: https://yhbt.net/yahns-public/
* nntp://news.public-inbox.org/inbox.comp.lang.ruby.yahns

lrg nabgure ubeevoyl-anzrq freire :>

Changes:

    yahns 1.16.0

    This release fixes warnings for users combining Rack::Deflater
    with HTTPS support:
        https://yhbt.net/yahns-public/20180714005630.11812-1-e@80x24.org/

    yahns-rackup(1) users may not specify "-O listen=inherit"
    when spawning from systemd.  The "listen" directive may
    be omitted entirely from the yahns-config(5) files.

    A few other cleanups and nothing interesting, otherwise.

    20 yawn-worthy changes since v1.15.0 (2017-03-23):
          config: more descriptive variable name
          proxy_pass: comment explaining what rack.hijack calls
          USR2 upgrades may use Process.spawn for vfork
          avoid Thread#[] and Thread#[]= across threads
          gemspec: declare Ruby 2.0+ dependency, here
          test_bin: SO_KEEPALIVE value only needs to be true
          rackup_handler: remove unnecessary branch
          test_bin: use RbConfig.ruby for non-standard names
          allow omitting specifying socket name when inheriting listen socket
          server: fix incomplete comment about SSLContext#setup
          test_rack_env: additional test for Rack environment
          test: allow setting TAIL env to watch error logs
          fix some unused variables
          tests: thread-safety fixes
          test/server_helper: describe reason for termination
          test/test_ssl: set SSLContext#security_level=0
          doc: https:// URLs instead of git://
          http_client: clear backtrace on "wrong version number" in OpenSSL
          openssl_client: do not attempt writes after SystemCallError
          use IO#pread if available in Ruby 2.5

    *ZZZZZZ*

Please note the disclaimer:

  yahns is extremely sensitive to fatal bugs in the apps it hosts.  There
  is no (and never will be) any built-in "watchdog"-type feature to kill
  stuck processes/threads.  Each yahns process may be handling thousands
  of clients; unexpectedly killing the process will abort _all_ of those
  connections.  Lives may be lost!

  yahns hackers are not responsible for your application/library bugs.
  Use an application server which is tolerant of buggy applications
  if you cannot be bothered to fix all your fatal bugs.

                 reply	other threads:[~2018-08-06  1:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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/yahns/README

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

  git send-email \
    --in-reply-to=20180806013210.GA27913@dcvr \
    --to=e@80x24.org \
    --cc=ruby-talk@ruby-lang.org \
    --cc=yahns-public@yhbt.net \
    /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/yahns.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).