about summary refs log tree commit diff stats
path: root/test/dummy/config/puma.rb
diff options
context:
space:
mode:
authorKelly Rauchenberger <fefferburbia@gmail.com>2017-09-16 18:46:55 -0400
committerKelly Rauchenberger <fefferburbia@gmail.com>2017-09-16 18:46:55 -0400
commit5e62e771bf14f58dd1622d2e3631309caa201349 (patch)
tree76143baae833a4cfe0e05cefb18b5a31d15b74e9 /test/dummy/config/puma.rb
downloadpokeviewer-5e62e771bf14f58dd1622d2e3631309caa201349.tar.gz
pokeviewer-5e62e771bf14f58dd1622d2e3631309caa201349.tar.bz2
pokeviewer-5e62e771bf14f58dd1622d2e3631309caa201349.zip
Initial commit
Diffstat (limited to 'test/dummy/config/puma.rb')
-rw-r--r--test/dummy/config/puma.rb56
1 files changed, 56 insertions, 0 deletions
diff --git a/test/dummy/config/puma.rb b/test/dummy/config/puma.rb new file mode 100644 index 0000000..1e19380 --- /dev/null +++ b/test/dummy/config/puma.rb
@@ -0,0 +1,56 @@
1# Puma can serve each request in a thread from an internal thread pool.
2# The `threads` method setting takes two numbers: a minimum and maximum.
3# Any libraries that use thread pools should be configured to match
4# the maximum value specified for Puma. Default is set to 5 threads for minimum
5# and maximum; this matches the default thread size of Active Record.
6#
7threads_count = ENV.fetch("RAILS_MAX_THREADS") { 5 }
8threads threads_count, threads_count
9
10# Specifies the `port` that Puma will listen on to receive requests; default is 3000.
11#
12port ENV.fetch("PORT") { 3000 }
13
14# Specifies the `environment` that Puma will run in.
15#
16environment ENV.fetch("RAILS_ENV") { "development" }
17
18# Specifies the number of `workers` to boot in clustered mode.
19# Workers are forked webserver processes. If using threads and workers together
20# the concurrency of the application would be max `threads` * `workers`.
21# Workers do not work on JRuby or Windows (both of which do not support
22# processes).
23#
24# workers ENV.fetch("WEB_CONCURRENCY") { 2 }
25
26# Use the `preload_app!` method when specifying a `workers` number.
27# This directive tells Puma to first boot the application and load code
28# before forking the application. This takes advantage of Copy On Write
29# process behavior so workers use less memory. If you use this option
30# you need to make sure to reconnect any threads in the `on_worker_boot`
31# block.
32#
33# preload_app!
34
35# If you are preloading your application and using Active Record, it's
36# recommended that you close any connections to the database before workers
37# are forked to prevent connection leakage.
38#
39# before_fork do
40# ActiveRecord::Base.connection_pool.disconnect! if defined?(ActiveRecord)
41# end
42
43# The code in the `on_worker_boot` will be called if you are using
44# clustered mode by specifying a number of `workers`. After each worker
45# process is booted, this block will be run. If you are using the `preload_app!`
46# option, you will want to use this block to reconnect to any threads
47# or connections that may have been created at application boot, as Ruby
48# cannot share connections between processes.
49#
50# on_worker_boot do
51# ActiveRecord::Base.establish_connection if defined?(ActiveRecord)
52# end
53#
54
55# Allow puma to be restarted by `rails restart` command.
56plugin :tmp_restart