From 0fdc22b9816511cb4c43bcaf52955476f07929f9 Mon Sep 17 00:00:00 2001
From: Yan <yanaung.nyein@code2lab.com>
Date: Tue, 21 Nov 2017 17:31:40 +0630
Subject: [PATCH] puma config

---
 config/puma.rb | 52 ++------------------------------------------------
 1 file changed, 2 insertions(+), 50 deletions(-)

diff --git a/config/puma.rb b/config/puma.rb
index 955320e4..f4d9b676 100755
--- a/config/puma.rb
+++ b/config/puma.rb
@@ -1,58 +1,10 @@
-application_path = '/home/superuser/Application/production/sxrestaurant'
+application_path = Rails.root
 directory application_path
 environment ENV.fetch("RAILS_ENV") { "development" }
 daemonize true
 pidfile "#{application_path}/tmp/puma/pid"
 state_path "#{application_path}/tmp/puma/state"
 stdout_redirect "#{application_path}/log/puma.stdout.log", "#{application_path}/log/puma.stderr.log"
+port        ENV.fetch("PORT") { 62158 }
 bind 'tcp://0.0.0.0:62158'
 workers 2
-
-# # 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 }.to_i
-# 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 number of `workers` to boot in clustered mode.
-# # Workers are forked webserver 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. If you use this option
-# # you need to make sure to reconnect any threads in the `on_worker_boot`
-# # block.
-# #
-# # preload_app!
-
-# # The code in the `on_worker_boot` will be called if you are using
-# # clustered mode by specifying a number of `workers`. After each worker
-# # process is booted this block will be run, if you are using `preload_app!`
-# # option you will want to use this block to reconnect to any threads
-# # or connections that may have been created at application boot, Ruby
-# # cannot share connections between processes.
-# #
-# # on_worker_boot do
-# #   ActiveRecord::Base.establish_connection if defined?(ActiveRecord)
-# # end
-
-# # Allow puma to be restarted by `rails restart` command.
-
-# plugin :tmp_restart