Closed odockal closed 3 years ago
We should not disable "server actions" if server is stopped. Many server actions may be valid (edit config file) when server is stopped.
We should trust our users to realize they have several servers configured on the same machine. They should be able to figure this out.
If possible, we can consider hiding the show-in-browser actions if the server is stopped. But I see this as an optional enhancement, not a bug. Users should be able to navigate their own workspaces here.
It is possible to add deployments and calls server action over stopped server adapter. This might lead to a confusions, as image this use case: