Reverse agent connection #467
AndreKR
started this conversation in
Feature Request
Replies: 1 comment 1 reply
-
I'll second this idea, but for a slightly different use case. I'd like to be able to deploy the remote dockge (agent) and have it connect to the main dockge installation automatically. This way you can easily add remote instances and have them show up on your main dockge UI. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
🏷️ Feature Request Type
Other
🔖 Feature description
Currently the main installation connects to the other agents, which requires all agents to be reachable from the main installation.
I have some edge hosts that are not reachable at all, but they can reach the main installation via internet.
✔️ Solution
There should be a dedicated agent application (or a configuration setting for the normal Dockge application that turns it into an agent) that will connect to the central Dockge installation, receive commands and send data.
❓ Alternatives
Of course I could set up Wireguard or Zerotier or something like that in addition to Dockge, but this means extra administrative overhead. Simply connecting via HTTPs to a websocket of the main Dockge installation also means you basically get SSL for free because you probably have already set it up for the UI.
📝 Additional Context
No response
Beta Was this translation helpful? Give feedback.
All reactions