We already discussed it somewhere else.
It doesn’t make sense that a UI modify the behavior of the other one.
Such cosmetic issue is present just because you have installed both the UI and you’re accessing both.
If you have already configured the machine using Cockpit, you can just press “next next next” on the nethgui wizard. If you want to totally skip it, just execute:
It would make sense that the final step in whatever manager would be to NOT trigger/bypass/set as ‘finsished initial setup’ the first config in another manager.
Then I must have some kind of misunderstanding what the first install wizard (on classic Servermanager) does.
If a first install wizard has been performed, why still show it on another Servermanager? Either way if it has been done on classic servermanager or new cockpit servermanager. When it’s done, it’s done. No need to do it double…
@davidep Now you are pushing it my friend. old school (wannabe) sysadmin here… and old habits don’t change easily…
of course, cold turkey removing the ‘old’ servermanager will force a lot of people to start using nethserver-cockpit. But to be honest, my default servermanager is still at port 980…
Even Nethgui wasn’t perfect when it was released. Cockpit is still a beta, everybody knows it has bugs. Indeed we’re working to provide missing features and fix the bugs. Hopefully it will be ready for a stable release in 7.8.
If that’s not true, we can wait 7.9… I think going on with two server managers is difficult for the support team. Even writing the docs is hard, because of the duplication of the interface.
I was the first to say let’s keep Nethgui forever and ever. That can be still true because it can be available from Software Center even after the decision to remove it from the ISO bundle will come. And, as said, existing installations can be left untouched.
