[FEATURE_REQUEST] Separate URL Targets for Service Access and Status Checking

[BercziSandor]

Is your feature request related to a problem? If so, please describe.

Status check is not working as expected, because... (see below)

Describe the solution you'd like

I am using mafl inside Docker, and I have a use case where the URL to open the service in the browser (for end users) differs from the URL needed for checking the service status internally.

For example:
Browser (end user) link: http://myserver.com:8096/web/#/home.html
Status check link (inside Docker or local network): http://127.0.0.1:8096/web/#/home.html

Currently, the link and the status use the same URL, so it’s not possible to specify two different targets—one for the user-facing link and one for the status check.
Would it be possible to add support in the configuration for specifying a separate status.link or status.target URL, distinct from the link shown on the homepage?
This feature would allow more flexible monitoring setups, especially for Dockerized environments or services behind proxies where the access URL differs from the internal status check URL.

Thank you for considering this feature! Looking forward to your thoughts.

Priority

Medium (Would be very useful)

Is this something you would be keen to implement

None

[hywax-assistant]

👋 @BercziSandor
Thanks for opening your first issue here!
To help make it easier for us to investigate your issue, please follow the contributing guidelines.

If you like this project, please ⭐ star our repo.

[Re4mstr]

I am waiting to integrate mafl to my stack once this feature is possible.

+1 for this!