[SWAG Dashboard] Any way to show the swag_address and public port(s) in an extra row under "Proxies"?

[GlassedSilver]

This would really be helpful to discern services when you work with manual setups a lot.

For example:

• services running not on the same docker host are accessed by IP of the secondary host
• services running in docker's default bridge network rather than all being on the same docker network to keep them more isolated

That way the public address is your reference, something that should always be rather identifiable.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[GlassedSilver]

Please kindly unstale this, thank you

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[GlassedSilver]

unstale please

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[GlassedSilver]

Bot begone :D

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[GlassedSilver]

unstale

[quietsy]

I didn't fully understand the request.
How can the dashboard know these details?
I can have a proxy for radarr.*, it will catch requests to any domains starting with radarr..