config/puma.rb
Line is too long. [93/80] Open
Open
# If you are using Rails 4.1+ you can use the database.yml to set your connection pool size- Exclude checks
Line is too long. [124/80] Open
Open
# This should point at your applications config.ru, which is automatically generated by Rails when you create a new project.- Exclude checks
Line is too long. [89/80] Open
Open
# Each Puma worker will be able to spawn up to the maximum number of threads you specify.- Exclude checks
Line is too long. [90/80] Open
Open
# Manage the external connections of each individual worker using the on_worker_boot calls- Exclude checks
Line is too long. [87/80] Open
Open
# This block is run after a worker is spawned, but before it begins to accept requests.- Exclude checks
Line is too long. [103/80] Open
Open
# With a typical Rails memory footprint, you can expect to run 2-4 Puma worker processes on a free dyno- Exclude checks
Line is too long. [113/80] Open
Open
# Puma forks multiple OS processes within each dyno to allow a Rails app to support multiple concurrent requests.- Exclude checks
Line is too long. [134/80] Open
Open
# Puma allows you to configure your thread pool with a min and max setting, controlling the number of threads each Puma instance uses.- Exclude checks
Line is too long. [126/80] Open
Open
# Heroku will set ENV['PORT'] when the web process boots up. Locally, default this to 3000 to match the normal Rails default.- Exclude checks