Feature/local port custom service

[nkay08]

Description

I often access my services not only via reverse proxy but also by port.
E.g. I access the service via URL if I am at home and if I want to access it remotely via wireguard, the DNS does not properly work, so I access the service via port.
Up until now, you could only specify one URL for a service in homer, so either the subdomain that is registered in the reverse proxy or the URL with the port.

I added a GenericWithPort custom service, where you can specify the url and the port. This adds a small footer to the service card which contains a link to the service via port.
Depending on the current base url where you are accessing homer, the link leads to the service on that port.

You can see some example screenshots below (the mouse cursor is not visible, but is hovering over the corresponding link, so you can see the url that it leads to).

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• I've read & comply with the contributing guidelines
• I have tested my code for new features & regressions on both mobile & desktop devices, using the latest version of major browsers.
• I have made corresponding changes to the documentation (README.md).
• I've checked my modifications for any breaking changes, especially in the config.yml file

Examples

Overview

Mouse hovering over the usual link

Mouse hovering over Port link