Service running on port 5000

[simonszu]

I have just discovered that the server inside the docker container starts on port 5000:

16:14:47 web.1  | started with pid 7
16:14:53 web.1  |  * Running on http://0.0.0.0:5000/ (Press CTRL+C to quit)
16:14:53 web.1  |  * Restarting with stat

Is this the desired behaviour? If yes, i'll update the Dockerfile and the readme and create a pull request. I was just wondering, since the Dockerfile and the Readme explicitly mention port 4000 for now.

[pquerner]

Yes, it says that for me aswell. In the end it doesnt matter what port its running on internally, since you use a proxy anyway. (Or should, since that will make things a lot easier)

[simonszu]

I do. The problem is that the dockerfile exposes port 4000. This is also shown in the docker ps list. However, good to know that it isn't my fault and that I can dock to port 5000 as well, although not explicitly exposed in the dockerfile. I will do the final steps of the setup tomorrow, I think.

On Sat, Mar 3, 2018, 22:31 Pascal Querner notifications@github.com wrote:

Yes, it says that for me aswell. In the end it doesnt matter what port its running on internally, since you use a proxy anyway. (Or should, since that will make things a lot easier)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/stevenleeg/geemusic/issues/193#issuecomment-370181447, or mute the thread https://github.com/notifications/unsubscribe-auth/AAqxI4h4awkuw-sPw4L2gnIGp1LTsxC3ks5tawvDgaJpZM4Sa_Mt .

-- Before printing this email, think if it is really needed.

[ashutoshmittal2309]

Yes, it looks like it uses 5000 as the default port instead of 4000. I tried both Docker and Foreman with same behavior.

[simonszu]

Fixed in https://github.com/stevenleeg/geemusic/pull/197