From 2c5d3bc48bfb82f5ba6114572f20f87f7425e9f3 Mon Sep 17 00:00:00 2001 From: Steven Harman Date: Thu, 9 May 2013 23:05:50 -0400 Subject: [PATCH] Add a note about multi-worker web servers --- README.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/README.md b/README.md index ddfbe38a..d5b81674 100644 --- a/README.md +++ b/README.md @@ -82,6 +82,19 @@ end [![Build Status](https://travis-ci.org/charliesome/better_errors.png)](https://travis-ci.org/charliesome/better_errors) +### Unicorn, Puma, and other multi-worker servers + +Better Errors works by leaving a lot of context in server process memory. If +you're using a web server that runs muliple "workers" it's likely that a second +request (as happens when you click on a stack frame) will hit a different +worker. That worker won't have the necessary context in memory, and you'll see +a `Session Expired` message. + +If this is the case for you, consider turing the number of workers to one (1) +in `development`. Another option would be to use `rails server`, or another +single-process web server, when you are trying to troubleshoot an issue in +development. + ## Get in touch! If you're using better_errors, I'd love to hear from you. Drop me a line and tell me what you think!