1
0
Fork 0
This repository has been archived on 2023-03-27. You can view files and clone it, but cannot push or open issues or pull requests.
lpr-partynest/config/puma/development.rb

36 lines
1.3 KiB
Ruby
Raw Normal View History

2018-11-22 14:58:12 -05:00
# frozen_string_literal: true
2018-11-28 16:11:00 -05:00
workers_count = ENV.fetch('WEB_CONCURRENCY') { 1 }
2018-11-22 15:00:34 -05:00
threads_count = ENV.fetch('RAILS_MAX_THREADS') { 5 }
2018-11-22 14:33:08 -05:00
# Specifies the number of `workers` to boot in clustered mode.
# Workers are forked webserver processes. If using threads and workers together
# the concurrency of the application would be max `threads` * `workers`.
# Workers do not work on JRuby or Windows (both of which do not support
# processes).
#
2018-11-28 16:11:00 -05:00
workers workers_count
# Puma can serve each request in a thread from an internal thread pool.
# The `threads` method setting takes two numbers: a minimum and maximum.
# Any libraries that use thread pools should be configured to match
# the maximum value specified for Puma. Default is set to 5 threads for minimum
# and maximum; this matches the default thread size of Active Record.
#
threads threads_count, threads_count
2018-11-22 14:33:08 -05:00
# Use the `preload_app!` method when specifying a `workers` number.
# This directive tells Puma to first boot the application and load code
# before forking the application. This takes advantage of Copy On Write
# process behavior so workers use less memory.
#
2018-11-28 16:11:00 -05:00
preload_app!
# Specifies the `port` that Puma will listen on to receive requests;
# default is 3000.
#
port ENV.fetch('PORT') { 3000 }
2018-11-22 14:33:08 -05:00
# Allow puma to be restarted by `rails restart` command.
plugin :tmp_restart