From e3b149fae611d9c66d3e41048970bd78f322cc9c Mon Sep 17 00:00:00 2001 From: Caley Woods Date: Wed, 19 Sep 2012 10:27:27 -0500 Subject: Update comment in example unicorn config The timeout was changed to 30 and the comment wasn't updated. Also I've seen several reports of this timeout not being long enough for quite a few people. It resulted in me getting a 502 bad gateway from nginx until I upped it. Perhaps could back to the default 60 would be better? I changed mine to 300, running on an AWS micro instance. --- config/unicorn.rb.example | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'config') diff --git a/config/unicorn.rb.example b/config/unicorn.rb.example index 23746d255b4..425dbf33f86 100644 --- a/config/unicorn.rb.example +++ b/config/unicorn.rb.example @@ -6,7 +6,7 @@ working_directory app_dir # worker spawn times preload_app true -# nuke workers after 60 seconds (the default) +# nuke workers after 30 seconds (60 is the default) timeout 30 # listen on a Unix domain socket and/or a TCP port, -- cgit v1.2.1