enhance(backend): allow disabling HTTP port completely

[eternal-flame-AD]

Resolves #910

[codecov]

Codecov Report

❌ Patch coverage is 0% with 16 lines in your changes missing coverage. Please review.
✅ Project coverage is 78.51%. Comparing base (1818c5d) to head (7a9978e).
⚠️ Report is 4 commits behind head on master.

Files with missing lines	Patch %	Lines
runner/runner.go	0.00%	16 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #911      +/-   ##
==========================================
- Coverage   78.70%   78.51%   -0.19%     
==========================================
  Files          57       57              
  Lines        2517     2523       +6     
==========================================
  Hits         1981     1981              
- Misses        397      403       +6     
  Partials      139      139              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[jmattheis]

Could this instead be a enabled setting similar to the one for TLS? Should be default true.

[eternal-flame-AD]

I guess so, but it would be called GOTIFY_SERVER_ENABLED=false which semantically sounds funny.

[IzumiSenaSora]

GOTIFY_SERVER_ENABLED=false it really looks confusing... Some may even think that "huh? My server disabled? :p"
But we can use like
GOTIFY_PLAIN_SERVER_ENABLED=false
Or
GOTIFY_HTTP_SERVER_ENABLED=false

[eternal-flame-AD]

What I am trying to say is the name of these keys are tied to the yaml hierarchy by the configor, so if we add a key side by side with the current "port" key it would be called GOTIFY_SERVER_SOMETHING, which I don't like.

But I guess we can use GOTIFY_SERVER_DISABLE_HTTP or GOTIFY_SERVER_HTTP_FUNC=on/off/redirect , both should be good options forward

[jmattheis]

I'm okay with GOTIFY_SERVER_DISABLE_HTTP but I'm questioning if we really need this functionality or can prevent the problems via a different solution. See #910 (comment)