From: Eric Wong <e@80x24.org>
To: raindrops-public@bogomips.org
Subject: [PATCH] examples: add yahns config, zbatery is abandoned
Date: Sun, 31 Jul 2016 15:11:13 +0000 [thread overview]
Message-ID: <20160731151113.26203-1-e@80x24.org> (raw)
Since zbatery is abandoned, point users towards yahns
instead since that is what I currently use.
---
examples/yahns.conf.rb | 30 ++++++++++++++++++++++++++++++
examples/zbatery.conf.rb | 5 ++++-
2 files changed, 34 insertions(+), 1 deletion(-)
create mode 100644 examples/yahns.conf.rb
diff --git a/examples/yahns.conf.rb b/examples/yahns.conf.rb
new file mode 100644
index 0000000..f5b4f10
--- /dev/null
+++ b/examples/yahns.conf.rb
@@ -0,0 +1,30 @@
+# Inlined rack app using yahns server (git clone git://yhbt.net/yahns.git)
+# Usage: yahns -c /path/to/this/file.conf.rb
+# There is no separate config.ru file for this example,
+# but rack_app may also be a string pointing to the path of a
+# config.ru file
+
+require 'rack'
+rack_app = Rack::Builder.new do
+ use Rack::Head
+ addr = %w(0.0.0.0:9418 0.0.0.0:443 [::]:443 0.0.0.0:80 [::]:80
+ 127.0.0.1:6081 127.0.0.1:280 0.0.0.0:119 [::]:119)
+ use Raindrops::Middleware, listeners: addr
+ run Raindrops::Watcher.new(listeners: addr)
+end.to_app
+# rack_app = '/path/to/config.ru' # a more standard config
+
+app(:rack, rack_app) do
+ # I keep IPv4 and IPv6 on separate sockets to avoid ugly
+ # IPv4-mapped-IPv6 addresses:
+ listen 8080
+ listen '[::]:8080', ipv6only: true
+ client_max_body_size 0 # no POST or any uploads
+ client_timeout 5
+ output_buffering false # needed for /tail/ endpoint to avoid ENOSPC
+ queue { worker_threads 30 }
+end
+
+# logging is optional, but recommended for diagnosing problems
+# stderr_path '/var/log/yahns/stderr-raindrops.log'
+# stdout_path '/var/log/yahns/stdout-raindrops.log'
diff --git a/examples/zbatery.conf.rb b/examples/zbatery.conf.rb
index 3f67c7a..5f94c0e 100644
--- a/examples/zbatery.conf.rb
+++ b/examples/zbatery.conf.rb
@@ -1,6 +1,9 @@
# Used for running Raindrops::Watcher, which requires a multi-threaded
# Rack server capable of streaming a response. Threads must be used,
-# so Zbatery is recommended: http://zbatery.bogomip.org/
+# so any multi-threaded Rack server may be used.
+# zbatery was recommended in the past, but it is abandoned
+# <http://zbatery.bogomip.org/>.
+# yahns may work as an alternative (see yahns.conf.rb in this dir)
Rainbows! do
use :ThreadSpawn
end
--
EW
reply other threads:[~2016-07-31 15:11 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/raindrops/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160731151113.26203-1-e@80x24.org \
--to=e@80x24.org \
--cc=raindrops-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/raindrops.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).