Set unusual port in uni-meter.conf as default

[DanielGlaas]

Per default, the port 80 is used for the HTTP access of both:

• unimeter /status endpoint
• the output device

If the host

• is already running something on port 80 or
• the port is blocked (privileged)

then it is non-obvious what configuration has to be changed to solve this error:

With this change, a non-error default port is set to 8008.

[DanielGlaas]

This was already an issue here:

• port 80 already in use - port changes doesn't have any effect uni-meter#169 (comment)
• Port 80 in use - despite changing the ports in docker-compose file? uni-meter#229

[sdeigm]

That might solve your problem with the already used port, but Storages like the Hoymiles MS-A2 and the NOAH 2000 will not work with a different Port than 80. I guess you are using a Marstek Storage which does not need the HTTP port at all. So changing this port to a different default is not an option.

[DanielGlaas]

Well, we have two different aspects of "working" in mind:

1. Starting without errors and with an error stack trace.
2. Doing the logic what I want for my local setup.

When using docker with a provided docker-compose.yaml combined with prepared uni-meter.conf and logback.xml, the common expectation is to have an application that runs without critical errors (see 1.).
The intention of this MR is to fulfill this expectation.

Caring about the functionality (see 2.), I totally agree with you that the currently given defaults (port 80) might fulfill the needs for some users while my adaption might not fulfill it. However, changing it back to explicitly 80 is maybe a much less effort than finding out what to do to get the startup error away.

These are my thoughts about that, feel free what to do with these ideas.