[Feature Request] - Composr Master / Composr Slave or Agent type support

[bennos1911]

First off, just want to say this is absolutely awesome work! Your UI is leagues ahead and just blazing fast compared to anything else I have used, and continue to use. I was very excited with my initial testing and at the thought of replacing portainer, dockge, and basically beszel! I understand this is a "for fun/love" type project - but worth a try checking if the following Main Feature is on your roadmap or ruled out for whatever reason.

Main Feature
Composr Master / Composr Slave or Agent type support

• Presently the "Containers" view is limited to only showing containers the composr host is running - and installing composr on subsequent docker hosts and adding as a "Host" only enables shortcut links to those separate web interfaces and doesn't show their containers in any consolidated view. Clicking on "Composr" and choosing the other instance attempts to connect but does so using the local IP from the users browser and not via the composr host network. Which for those of us running reverse proxies would require setting up separate rules for each subsequent composr instance, dns, fw rules...etc.

Is the type of functionality where you could have one master Composr and enabling remote docker.sock access (or any other way) for Composr agents a potential development ? I am aware of the risks some will raise with remote docker.sock access - but this is a homelab after all :)

That feature would be a game changer for me and I would definitely donate what I can afford (~100USD) to help support you and its development. I know that amount isn't much but if you had 10 others like me offering the same, that amount adds up really quickly :D !

Regardless, thank you for your efforts! FOSS developers like you are dead set legends!

[Vansmak]

Yes the current state of just linking composers was a compromise until I figure it out.

[Vansmak]

Progress is being made