From dd993b74481e158bee3a7105ca85bdb01e5f61fe Mon Sep 17 00:00:00 2001 From: TheAssassin Date: Tue, 16 May 2017 22:16:46 +0200 Subject: [PATCH] Fix issue mentioned in osem/pull/1407 After the rebase (to update the PR with the latest changes), I had the same issue @lguerard has had. I noticed that the rails server didn't lisen on all interfaces any more, but bound the port to the loopback device only. By adding the parameter `-b 0.0.0.0`, I restored the previous behavior, and OSEM could be reached with the browser after it started up (takes a few seconds). --- docker/init.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docker/init.sh b/docker/init.sh index 81ab11b5..8f1ba766 100644 --- a/docker/init.sh +++ b/docker/init.sh @@ -45,4 +45,4 @@ echo ">>> Precompiling assets..." bundle exec rake assets:precompile echo ">>> Starting application server..." -exec bundle exec rails server -e production -p 9292 +exec bundle exec rails server -e production -b 0.0.0.0 -p 9292