"HOST" environment variable

[Cyanoure]

Hi!
I added the "HOST" environment variable. It works the same way as the "PORT".
I also added tests for it depending on "PORT" tests.

Fixes #6422

[codecov]

Codecov Report

Merging #6423 (6c270ea) into main (eb498b0) will increase coverage by 0.02%.
Report is 1 commits behind head on main.
The diff coverage is 100.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6423      +/-   ##
==========================================
+ Coverage   73.61%   73.64%   +0.02%     
==========================================
  Files          31       31              
  Lines        1880     1882       +2     
  Branches      406      407       +1     
==========================================
+ Hits         1384     1386       +2     
  Misses        419      419              
  Partials       77       77              

Files Changed	Coverage Δ
src/node/cli.ts	90.90% <100.00%> (+0.06%)	⬆️

---

Continue to review full report in Codecov by Sentry.

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

[code-asher]

Thank you! I love the addition of tests as well.

What do you think about making this CODE_SERVER_HOST instead? I know we already have plain PORT but we are trying to ensure new variables have unique names (and eventually we should add CODE_SERVER_PORT and deprecate PORT too).

[Cyanoure]

Thank you! I love the addition of tests as well.

What do you think about making this CODE_SERVER_HOST instead? I know we already have plain PORT but we are trying to ensure new variables have unique names (and eventually we should add CODE_SERVER_PORT and deprecate PORT too).

I think it will be fine.
But for the port, I don't know. I mean, in the past when I tried Heroku, it used PORT. I had to use that environment variable to set the listening port of my nodejs server.
I don't know if anyone uses code-server in an environment like that.

Thanks for the review!

[code-asher]

Thank you for the input and the examples! Collisions like that are a really good reason we should use a unique prefix.

For this PR let us go forward with CODE_SERVER_HOST, then. No need to make any changes to PORT here (unless you want to), I can do that in another PR.

[code-asher]

Oh wait, were you saying that Heroku sets PORT so we actually should keep PORT? I think I misunderstood it as Heroku itself using PORT and that was colliding with code-server.

[Cyanoure]

Oh wait, were you saying that Heroku sets PORT so we actually should keep PORT? I think I misunderstood it as Heroku itself using PORT and that was colliding with code-server.

Yes :D
I'm sorry if I was unclear.

Then I'll add a new commit for replacing HOST to CODE_SERVER_HOST.

[code-asher]

Thanks again, looks good!

Sounds like we will probably want to keep PORT around then. I will keep that in mind!