Sutty/trabajo-afectivo
5
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

It seems to be a bug in puma 3.0.2, not able to use own --pid param.

Browse source
This commit is contained in:
Martin Edenhofer 2016-03-02 10:43:51 +01:00
parent 7dcd98a5e8
commit f4f99306b9
2 changed files with 3 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
script/build/test_shutdown.sh
View file

@ -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

3
script/build/test_startup.sh
View file

@ -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