fix #5399 Strapi is not using the configured host when launching the server

[fodkastir]

Description of what you did:

Strapi does not the host value in the configuration when launching the server currently. Therefore, Node server listens on all interface when host value is omitted. This causes a problem when the user has other applications that run on the same port but different interfaces.

Fix #5399.

[derrickmehaffy]

I'm fine with this change, but something to note that if users (improperly) configured their host without the proxy block this will break their applications.

(As in using a domain instead of an IP binding)

Maybe something to note in a migration guide.

Edit: Also for production/staging, docs need to be made to explain on setting their host to something like 0.0.0.0 especially in cases like heroku

[alexandrebodin]

Hi @fodkastir, can you please mention the issue you are fixing in your comment :)

[codecov]

Codecov Report

Merging #5486 into master will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #5486   +/-   ##
=======================================
  Coverage   17.73%   17.73%           
=======================================
  Files         687      687           
  Lines       10151    10151           
  Branches     1643     1643           
=======================================
  Hits         1800     1800           
  Misses       6961     6961           
  Partials     1390     1390           

Flag	Coverage Δ
#front	13.14% <ø> (ø)
#unit	37.04% <ø> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 44b1b30...222903b. Read the comment docs.

[fodkastir]

@alexandrebodin I have edited my comment.

[alexandrebodin]

@fodkastir I meant can you add a link to the issue :)

[fodkastir]

@alexandrebodin got it and it is done.

[alexandrebodin]

LGTM