-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Terminal User Interface equivalent to cockpit #21000
Comments
Cockpit has no interest in providing a TUI, this would be a lot of work for the Cockpit team to develop, maintain. If you have a machine without networking you can still access Cockpit via a local browser on localhost. |
Thank you for your sincerity! |
@jelly how do you suggest doing this on a minimal install with no GUI or web browser installed? |
I would need to know more about your use case but you could setup a bastion host so you only have to run |
Why not think on a front-end ncurses for cockpit APIs that already exists? Consume those APIs via loopback... |
Feel free to give it a try, but it's a lot of work for us and we have no plans in that direction. |
To those who needs to deploy and maintain remotely appliances and virtual appliances depending on end user interactions, cockpit is a dream!
A thing that avoid several unnecessary access through vnc/anydesk and etc.
But, there is still a small part that is still a pain.
When network is not available by some reason, cockpit is also unavailable...
So, I imagine that a TUI version of the core of cockpit, ncurses based... With the same goals os the console of VMware ESXi, would be a great thing.
I imagine for example that the same Network Manager the is used on web-gui, will adequately replaced by nm-tui.
So... Is this a this that very far from the objectives of cockpit project?
The text was updated successfully, but these errors were encountered: