https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# hobbyfarm
a
This message was deleted.
f
Regarding the first scenario: There is no such feature in hobbyfarm as of today.
👍 1
regardind the second scenario: i never came across this usecase, but i think this is not possible with the current setup. The only thing i could imagine is using public IP VMs and not using the webinterface proxy
👍 1
m
OK, that makes sense. I wanted to make sure I wasn’t missing anything before I went down any paths to attempt to solve the problem. Thank you, as always, for your quick responses. 🙂
✅ 1
w
For the second scenario, are you attempting to obtain TLS for the IPs of the VMs?
f
we could really improve the terminals again: splitting the terminal in two terminals, opening the terminal in a new tab etc. for all RDP connections this would be great as they sometimes are to small on smaller screens
🔥 1
m
@worried-fountain-60974 In the current configuration, we run a series of Ansible commands to generate an ACME certificate via a DNS challenge per VM, as each VM is assigned a unique DNS in CloudFlare.
@faint-optician-47536 @worried-fountain-60974 Following up from yesterday, I’ve been spending some time with tmux and think that we can probably solve the issues by using the 
:set -g mouse on
on the command line. This gives us the ability to use the mouse to bring up a tmux context menu to split the screen, move between splits, kill splits, etc. This also allows the user to click between the windows using the mouse. However, the limitation that I’m running into when you right click on the terminal, the browser context menu also appears, preventing the use of the tmux context window. Is there an easy way in HobbyFarm to disable the ability bring up the browser context menu on the terminal window and/or the application as a whole?
f
It would be possible to disable the browser context. But why would we try to do this? Some users have problems copying from inside the terminal using ctrl+c, so they need the copy function from the browser context menu
m
Sorry, I think I didn’t convey my thoughts correctly. I’m not looking to implement as a feature, but wanted to see if there was an existing way to do so, possibly by passing JS in some way on the deployment of the UI pod.
f
Okey got it. There is currently no way to pass JS to the UI. I could see this as a user setting, where the user could enable and disable the in-build browser context
👍 1
m
In our use-case, we don’t have a need to use the browser context menu, and as shown in the screenshot, it overlays on top of the tmux context window that we would want to use. I was just looking to see if there may be an easy way to disable it without extra work.
2 Views
Open in Slack
PreviousNext
Powered by