From f4f99306b92368dd53cd82ca624284edbe23ce3d Mon Sep 17 00:00:00 2001 From: Martin Edenhofer Date: Wed, 2 Mar 2016 10:43:51 +0100 Subject: [PATCH] It seems to be a bug in puma 3.0.2, not able to use own --pid param. --- script/build/test_shutdown.sh | 2 +- script/build/test_startup.sh | 3 ++- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/script/build/test_shutdown.sh b/script/build/test_shutdown.sh index ed4c900a7..deb07be6c 100755 --- a/script/build/test_shutdown.sh +++ b/script/build/test_shutdown.sh @@ -6,7 +6,7 @@ EXIT=$4 || 0 script/scheduler.rb stop script/websocket-server.rb stop -kill $(cat tmp/pids/puma.pid) +kill $(cat tmp/pids/server.pid) rake db:drop diff --git a/script/build/test_startup.sh b/script/build/test_startup.sh index de5558c6b..9062bdec5 100755 --- a/script/build/test_startup.sh +++ b/script/build/test_startup.sh @@ -15,6 +15,7 @@ echo "export RAILS_ENV=$RAILS_ENV" echo "export IP=$IP" echo "export BROWSER_PORT=$BROWSER_PORT" -rails s puma -d --pid tmp/pids/puma.pid --bind 0.0.0.0 --port $APP_PORT +#rails s puma -d --pid tmp/pids/server.pid --bind 0.0.0.0 --port $APP_PORT +rails s puma -d --bind 0.0.0.0 --port $APP_PORT script/websocket-server.rb start -d -p $WS_PORT script/scheduler.rb start