agenda-libre-ruby/config/puma.rb

40 lines
1.5 KiB
Ruby
Raw Normal View History

2017-10-21 22:12:29 +02:00
# 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.
#
2019-12-21 21:00:16 +01:00
max_threads_count = ENV.fetch('RAILS_MAX_THREADS') { 5 }
min_threads_count = ENV.fetch('RAILS_MIN_THREADS') { max_threads_count }
threads min_threads_count, max_threads_count
2017-10-21 22:12:29 +02:00
# Specifies the `port` that Puma will listen on to receive requests; default is
# 3000.
#
port ENV.fetch('PORT') { 3000 }
# Specifies the `environment` that Puma will run in.
#
environment ENV.fetch('RAILS_ENV') { 'development' }
2019-12-21 21:00:16 +01:00
# Specifies the `pidfile` that Puma will use.
pidfile ENV.fetch('PIDFILE') { 'tmp/pids/server.pid' }
2017-10-21 22:12:29 +02:00
# Specifies the number of `workers` to boot in clustered mode.
2019-12-21 21:00:16 +01:00
# Workers are forked web server processes. If using threads and workers together
2017-10-21 22:12:29 +02:00
# 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).
#
# workers ENV.fetch("WEB_CONCURRENCY") { 2 }
# 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
2019-12-21 21:00:16 +01:00
# process behavior so workers use less memory.
2017-10-21 22:12:29 +02:00
#
# preload_app!
# Allow puma to be restarted by `rails restart` command.
plugin :tmp_restart