WeTTY - Better usage option - in my humble opinion

As WeTTY is available as an OMV plugin, which is handy, and also we now have cli/exec access in the Compose plugin.

I've wanted for some time a better way of accessing a shell, now I know just because other NAS and Hypervisors have certain feature doesn't mean that OMV always needs them. But the more I see Truenas, Unraid, Proxmox etc have a 1 click access to a shell, which logs in as the currant user.

So I'd like to suggest, that the WeTTY/Open UI button be added to the side menu below the Dashboard button AND/OR the main notification/power menu bar(my preference, as not everyone has the menu displayed). It could be renamed, perhaps to 'Terminal' or 'CLI' or just a icon of a terminal.

I would also like to see more options in the WeTTY settings page -

Add A checkbox option to login automatically (as I now know about, as I was lectured about recently), so user and password input would be saved.

Add A checkbox option to login automatically as currant user. (My preferred option)

I know people will say that login automatically is insecure, but someone already has access to the OMV dashboard, you're already in trouble.

Unfortunately I severely lack programming skills, but to me, it doesn't look as though much would need to be added - A button and a couple more settings in the WeTTY settings, if users didn't install WeTTY then nothing would change.

This is just a suggestion, if no OMV user agrees or the developers don't think this is worth it, then I'm fine with that, but I really do think it would be a useful and great addition to getting shell access to OMV.

Quote from ryecoaaron

The problem is you can go to the wetty interface without even logging into the omv web interface. That is one reason why it has a separate login.

I understand that. That could stay the same, you would only be able to auto login when using the button from within OMV.

Quote from ryecoaaron

you could just bookmark the wetty url.

I know, but it's still not within the OMV Eco system, I'd prefer and think its' a better solution to use a button from the main interface.

But if no-one else agrees, then its fine.I'll just carry on as I do now. It's not something that will stop me from using OMV.

As the thread the 'Adding a terminal (cli) to OMV in general' has been locked and ryecoaaron has just said 'it was relatively easy to add a host shell to the compose plugin's exec terminal' and allowed access to the host OS from the container list..

I'd like to thank him for his effort!!!

It works well, I really hope ryecoaaron might consider adding this option as I've outlined in the opening message. But as I received some quite negative comments, I don't blame him leaving it where it is.

Thanks ryecoaaron.