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.

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.
Caley Woods
1 parent bf625b7c
Showing 1 changed file with 1 additions and 1 deletions Show diff stats
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,
...	...	@@ -6,7 +6,7 @@ working_directory app_dir
6	6	# worker spawn times
7	7	preload_app true
8	8
9		-# nuke workers after 60 seconds (the default)
	9	+# nuke workers after 30 seconds (60 is the default)
10	10	timeout 30
11	11
12	12	# listen on a Unix domain socket and/or a TCP port,
...	...