* Upgrade Rails to 6.1 * Switch to unreleased bullet * Run rails app:update * Add deprecation notices after reading changelogs * Fix app:update error * Move middleware in the correct place * Temporarily disable ransack which does not support Rails 6.1 * Remove wrongly merged file * Re-run spring binstub * Fix double quotes * Track ransack branch with Rails 6.1 support * Fix deprecation * Switch to Ransack 2.4 which supports Rails 6.1 rc1 * Fix missing default params for the duration substitution * Fix new behavior of relation.pluck with contradictory queries * Fix uploaders specs by tracking rspec-rails main repo * Disable bullet temporarily * Fix remaining fixture_file_upload usages * Add default seconds for video article duration * Trigger Travis CI * Upgrade Rails to 6.1.0.rc2 * Remove file deleted on master * Add Rails 6.1 gem to Gemfile * Trigger Travis CI * Revert "Disable bullet temporarily" This reverts commit cee0c2ce61fb72cbc16d52c94b12ee681e873031. * Fix bullet version * Upgrade to acts-as-taggable 7 and fix conflict * Update Gemfile and rspec-* gems * Fix nokogiri in Gemfile.lock * Switch to rspec-rails main branch * Remove leftover vendored cached items * Fix path for Rails 6.1 * Use latest release of erb_lint * Re-run rails app:update to incorporate new changes * Disable erb_lint's ErbSafety checks * Fix Gemfile.lock and re-add platform specific gems of Nokogiri * Add mini_portile2 as well * Fix latest merge conflict by removing now unused faraday_middleware * Upgrade to Rails 6.1.3.1 * Regenerate Gemfile.lock and vendor/cache * Add x86_64 linux gem * Mark spec as flaky * Revert "Mark spec as flaky" This reverts commit 3caba94b33645f9b59c84ba78ee8df042fc7aee0. Co-authored-by: Mac Siri <krairit.siri@gmail.com>
47 lines
1.8 KiB
Ruby
47 lines
1.8 KiB
Ruby
# 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_count = ENV.fetch("RAILS_MAX_THREADS", 5)
|
|
threads threads_count, threads_count
|
|
|
|
# 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" }
|
|
|
|
# Specifies the `pidfile` that Puma will use.
|
|
pidfile ENV.fetch("PIDFILE") { "tmp/pids/server.pid" }
|
|
|
|
# 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)
|
|
|
|
# calls GC a handful of times and compacts the heap on Ruby 2.7+ before forking.
|
|
# This may reduce memory usage of Puma on MRI.
|
|
nakayoshi_fork
|
|
|
|
# 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
|
|
|
|
on_worker_boot do
|
|
# Worker specific setup for Rails 4.1+
|
|
# See: https://devcenter.heroku.com/articles/deploying-rails-applications-with-the-puma-web-server#on-worker-boot
|
|
ActiveRecord::Base.establish_connection
|
|
end
|