Replies: 6 comments 2 replies
-
The expectation with the current design is that an agent will communicate with one hub. Considering your scenario, I agree that one agent connecting to multiple hubs would be ideal. I'll try to add support for this in the next release. I'm visiting family right now so it may be a few weeks. |
Beta Was this translation helpful? Give feedback.
-
Hey @henrygd , just wondering if you had a chance to look into this? |
Beta Was this translation helpful? Give feedback.
-
This would be really helpful. In my case, I have a few servers for my clients (I'm a freelancer) and I would like the agent to report to the individual hubs but I also want to have a global hub for all servers. Thanks for making this project so cool and easy to use |
Beta Was this translation helpful? Give feedback.
-
This has been added. New release will be out later today if I have time to update the docs and release notes, otherwise tomorrow. |
Beta Was this translation helpful? Give feedback.
-
This should work now in 0.10.0. Separate your keys with a new line using Let me know if you have any trouble with it! |
Beta Was this translation helpful? Give feedback.
-
It worked perfectly fine for me! Thank you very much for this excellent work. It would be great to add an example of this in beszel.dev, it would also be good to document that the file in KEY_FILE supports blank lines and comments with # (I have read the code) It can be very useful for everyone |
Beta Was this translation helpful? Give feedback.
-
Hi. i have 2 beszel servers running. One on-site and one off-site.
Both areas are connected via a site-to-site VPN, and reachable by IP.
Is it possible to have my beszel agent on one of my servers report to both beszels (offsite and onsite) without having to run 2 separate docker containers? (It's an old raspbery pi, so running 2 agents seems like a waste of the limited resources.
Beta Was this translation helpful? Give feedback.
All reactions