diff options
| author | Eric Wong <e@80x24.org> | 2015-01-10 04:27:20 +0000 |
|---|---|---|
| committer | Eric Wong <e@80x24.org> | 2015-01-10 04:34:03 +0000 |
| commit | c0d431d22ee1e2e69338189f9ce5a4b4abc07e6e (patch) | |
| tree | 007022f0869232880d196efe6353aef71d0ba449 /SIGNALS | |
| parent | 633b984a41cc3b036b47982ad72b5658ec54c918 (diff) | |
| download | rainbows-c0d431d22ee1e2e69338189f9ce5a4b4abc07e6e.tar.gz | |
wrongdoc was difficult to maintain because of the tidy-ffi dependency and the HTML5 changes in Darkfish could not be handled well by Tidy. olddoc is superior as it generates leaner HTML which loads faster, requires less scrolling and less processing power to render. Aesthetic comparisons are subjective of course but completely unimportant compared to speed and accessibility. The presence of images and CSS on the old (Darkfish-based) site probably set unreasonable expectations as to my ability and willingness to view such things. No more, the new website is entirely simple HTML which renders well with even the wimpiest browser (hell, olddoc even tries to generate readable raw HTML).
Diffstat (limited to 'SIGNALS')
| -rw-r--r-- | SIGNALS | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -5,7 +5,7 @@ the signals Rainbows! uses internally to communicate with the worker processes are documented here as well. With the exception of TTIN/TTOU, signal handling matches the behavior of and {nginx}[http://nginx.net/] so it should be possible to easily share process management scripts -between \Rainbows!, Unicorn and nginx. +between \Rainbows!, unicorn and nginx. === Master Process @@ -60,7 +60,7 @@ automatically respawned. * USR1 - Reopen all logs owned by the worker process. See Unicorn::Util.reopen_logs for what is considered a log. - Unlike Unicorn, log files are reopened immediately in \Rainbows! + Unlike unicorn, log files are reopened immediately in \Rainbows! since worker processes are likely to be serving multiple clients simutaneously, we can't wait for all of them to finish. @@ -68,7 +68,7 @@ automatically respawned. You may replace a running instance of rainbows with a new one without losing any incoming connections. Doing so will reload all of your -application code, Unicorn/Rainbows! config, Ruby executable, and all +application code, unicorn/Rainbows! config, Ruby executable, and all libraries. The only things that will not change (due to OS limitations) are: |