upstart is dead!
upstart as system init - last release - 14.04 LTS, public support ending April 2019
upstart as user init - last release - 16.04 LTS, public support ending April 2021
Signed-off-by: fliiiix <hi@l33t.name>
Co-authored-by: Nate Berkopec <nate.berkopec@gmail.com>
When starting to transition from Unicorn to Puma, I first tried out
puma in development. I initially assumed from skimming the docs that
the number of workers for single mode should be 1. This led to our
developers not being able to kill their puma server properly in our
dev environment via Ctrl+C since the master process would stick
around and try to revive it.
Upon reading the docs more carefully and checking out the issues,
I found [I wasn't alone][issue-on-single-mode]. While it's obvious
that 1 worker implies the existence of a master process, when you're
just starting out it might take you a little while before you get
your head around single mode versus cluster mode and having the
configuration clearly stated helps with that imo.
So to make it blatantly obvious how to run puma in single mode,
I've added a line to the docs to explain it.
[issue-on-single-mode]: https://github.com/puma/puma/issues/1364
Measure the time spent reading the HTTP request body and expose it to the Rack app as `env['puma.request_body_wait']`.
This can be combined with a timestamp from a upstream proxy to get an indication of how long a request was waiting for a Puma thread to become available.
Fixes https://github.com/puma/puma/issues/1541
