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.
7 threads_count = ENV.fetch("RAILS_MAX_THREADS") { 5 }
8 threads threads_count, threads_count
10 # Specifies the `port` that Puma will listen on to receive requests; default is 3000.
12 port ENV.fetch("PORT") { 3000 }
14 # Specifies the `environment` that Puma will run in.
16 environment ENV.fetch("RAILS_ENV") { "development" }
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
24 # workers ENV.fetch("WEB_CONCURRENCY") { 2 }
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.
33 # Allow puma to be restarted by `rails restart` command.