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#
 7max_threads_count = ENV.fetch("RAILS_MAX_THREADS") { 5 }
 8min_threads_count = ENV.fetch("RAILS_MIN_THREADS") { max_threads_count }
 9threads min_threads_count, max_threads_count
10
11# Specifies the `worker_timeout` threshold that Puma will use to wait before
12# terminating a worker in development environments.
13#
14if ENV.fetch("RAILS_ENV", "development") == "development"
15  worker_timeout 3600
16end
17
18# Specifies the `port` that Puma will listen on to receive requests; default is 3000.
19#
20port ENV.fetch("PORT") { 3000 }
21
22# Specifies the `environment` that Puma will run in.
23#
24environment ENV.fetch("RAILS_ENV") { "development" }
25
26# Specifies the `pidfile` that Puma will use.
27pidfile ENV.fetch("PIDFILE") { "tmp/pids/server.pid" }
28
29# Specifies the number of `workers` to boot in clustered mode.
30# Workers are forked web server processes. If using threads and workers together
31# the concurrency of the application would be max `threads` * `workers`.
32# Workers do not work on JRuby or Windows (both of which do not support
33# processes).
34#
35workers ENV.fetch("WEB_CONCURRENCY") { 2 }
36
37# Use the `preload_app!` method when specifying a `workers` number.
38# This directive tells Puma to first boot the application and load code
39# before forking the application. This takes advantage of Copy On Write
40# process behavior so workers use less memory.
41#
42preload_app!
43
44# Allow puma to be restarted by `rails restart` command.
45plugin :tmp_restart