amatriain/feedbunch

# 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.
#
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

environment = ENV.fetch('RAILS_ENV') { 'development' }

# Specifies the `port` that Puma will listen on to receive requests, default is 3000.
# In production bind to a unix socket instead
#
if environment != 'production'
  port        ENV.fetch('PORT') { 3000 }
else
  # Bind to a local port if the PORT env variable is set.
  # If PORT is not set, bind to a local unix socket (needs a web server frontend)
  if ENV.has_key? 'PORT'
    port ENV.fetch('PORT')
  else
    bind 'unix:///tmp/feedbunch-puma.sock'
  end

  # Set release directory so puma can pick up changes when running phased restarts
  # Can be set with the APP_DIR env variable (optional)
  directory ENV.fetch('APP_DIR') { '/var/rails/feedbunch/current' }

  # Redirect output to log files
  # Can be set with the STDOUT_FILE and STDERR_FILE env variables (optional)
  stdout_file = ENV.fetch('STDOUT_FILE') { '/var/log/feedbunch-puma.log' }
  stderr_file = ENV.fetch('STDERR_FILE') { '/var/log/feedbunch-puma-error.log' }
  stdout_redirect stdout_file, stderr_file, true

  # Save a pidfile so init system can manage service
  pidfile '/tmp/feedbunch-puma.pid'
end

# Specifies the number of `workers` to boot in clustered mode.
# Workers are forked web server 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).
#
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
# process behavior so workers use less memory.
#
# preload_app!

# Allow puma to be restarted by `rails restart` command.
plugin :tmp_restart