From 55edd8a57148449036251cbb200bfc91c820508d Mon Sep 17 00:00:00 2001 From: Henne Vogelsang Date: Wed, 27 Mar 2019 10:58:10 +0100 Subject: [PATCH] Change how we start puma Puma is integrated with rails server, no need to start it manually. Takes care of logging etc. We also shouldn't run multiple workers unless we absolutely want to. --- Procfile | 2 +- config/puma.rb | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Procfile b/Procfile index 84cab0c9..8b9e764c 100644 --- a/Procfile +++ b/Procfile @@ -1,2 +1,2 @@ -web: bundle exec puma -C config/puma.rb +web: bundle exec rails server -b 0.0.0.0 worker: bundle exec rails jobs:work diff --git a/config/puma.rb b/config/puma.rb index fa11fb8f..9886e1e5 100644 --- a/config/puma.rb +++ b/config/puma.rb @@ -21,7 +21,7 @@ environment ENV.fetch("RAILS_ENV") { "development" } # Workers do not work on JRuby or Windows (both of which do not support # processes). # -workers ENV.fetch("WEB_CONCURRENCY") { 2 } +workers ENV.fetch("WEB_CONCURRENCY") { 1 } # Use the `preload_app!` method when specifying a `workers` number. # This directive tells Puma to first boot the application and load code