if I can explain myself a little, the discussion is going in all directions
Yes, I agree that Yast HTTP was not perfect. On top of that, I wanted to do a fun configuration, namely virtual instances on the same internal IP address, because I was helping friends or associations build their websites and I needed a test area. I realized that I had to go through the editor and write the vhost.conf file and the online commands. But Yast was useful to get started. Regarding the DNS, there is nothing in the cockpit. I’m talking about BIND the server, and if there’s one thing that isn’t “user friendly,” it’s the BIND settings!!
In summary, it is not desirable that Yast’s management tools are not rolled over into leap 16.x. AND if some were not perfect, it’s the opportunity with this technological leap from 16.x.
Google stole Linux and managed to impose it on smartphones, only thanks to the user interface. Back to M$ Windows NT, a “daube” adopted thanks to the mouse
That is expected of Open Chat discussions, especially with the way it was started. 
YaST’s Apache module was certainly a useful starting point for basic virtual host configuration, although more advanced setups still required editing the configuration files directly. As for BIND, I agree there isn’t currently an equivalent Cockpit module. If that’s functionality people value, then that’s exactly the kind of feature that could be proposed for Cockpit.
Well, maybe you can sending love, or support, to things like https://github.com/josephoaks/Cockpit-DNS_Bind
Good find. I stand corrected. 
Some of these modules are just not yet packaged fro openSUSE consumption.
Unbelievable what utter nonsense some users are producing…
And such stuff disqualifies for all technical discussions. Its kindergarten behaviour…
Please translate that correctly.
It’s got nothing to do with stealing.
If you translate it correctly, the meaning is different. Then it’s correct too.
sorry for my poor english
Google c’est emparé de linux
It does no longer surprise me. Not in the least
That’s insulting kids in kindergarten. Paraphrasing the bible: “Stupiditas stupiditatum et omnia stupiditas”.
But, let’s also look at ourselves, we have been tolerating / not addressing this bashing and shaming of MS, Apple, other linux distros for way too long as innocent humour. Now, imagine:
- you’ve always been a happy Windows user, but your laptop does not support Windows 11. At some birthday gathering you meet a person that has a way to keep using your otherwise fine laptop, i.e. $whatever_linux_distro.
- you decide to make the jump, start reading a bit, and land in an environment where people basically tell you you’ve been stupid and ignorant all those years.
I’ll put it more bluntly: this selfproclaimed superiority towards new users, devs, packagers, other distros, OSs, DEs is nothing more than an implicit expression of lack of selfconfidence. To all of those who think that this ranting here leads to anything, I’d say: “You don’t have to be here, run this distro. You are as free to go somewhere else as any other person”. I care about all those that want to bring this project forward based on its own merits.
This is in german with hoogle translater:
Zusammenfassend lässt sich sagen: Es wäre nicht wünschenswert, wenn die YaST-Verwaltungstools nicht in Leap 16.x übernommen würden. Und sollte es bei einigen davon Mängel gegeben haben, bietet dieser Technologiesprung zu 16.x die Gelegenheit, dies zu korrigieren.
Google hat sich Linux angeeignet und es auf Smartphones durchgesetzt – und das einzig dank der Benutzeroberfläche. Man denke nur an M$ Windows NT: ein eigentlich miserables System, das sich nur dank der Maus durchsetzen konnte.
Now, if I take the sentence:
“Google hat sich Linux angeeignet”
Well, that’s got nothing to do with stealing.
It just means that Google used Linux for its Android. And that’s probably undeniable.
Quite amusing to use Google to assess something about Google, but since this is Open Chat, let’s check what it does with Italian.
The initial English statement translates to:
Google ha rubato Linux ed è riuscita a imporlo sugli smartphone
which is definitely “stolen”, past participle of “steal”, but the French amendment translates to:
Google ha acquisito Linux
which is more like “acquiring”, “buying” or otherwise “get control over…”
and Google translates back to:
Google has taken over Linux
So much for why we still don’t have (and likely cannot have) the United States of Europe
Goodness me. I didn’t want to start a philosophical debate here. I just didn’t want people to always assume the worst. And I didn’t want people to constantly accuse others of the worst possible motives just so they can cast them in a bad light and denounce them. Especially when they don’t agree with what’s been written.
Or perhaps you simply aren’t 100% fluent in the foreign language, as it isn’t your mother tongue (and I include myself in that), which then leads to misunderstandings.
(This has been translated using Deepl)
The whole concept of FOSS and the FOSS licensing is that anyone is free to fork, modify or such. Also Google ( linux as base for Android ), Apple ( BSD as base for OSX ). Legally it’s only comparable to stealing if one changes the licenses to proprietary and then start suing the creators. And what AI says about that doesn’t matter, it is 100% wrong. Repeating that here or where ever is spreading false information.
OK folks, let’s stop here; I just wanted to reinforce that
so we must be quite tolerant with misunderstandings since actually in this “English” subforum there are few native English speakers. [Written by somebody that can barely understand those living 100 km from here if both of us speak the local dialect strictly ]
Okay, yea, it is “Open Chat” … but it has drifted horribly.
And now, folks are complaining about language use and how to properly interpret other languages.
This section is the English option. If any folks prefer conversing in German or French, or any other language … then post (elsewhere) in the language of your native choice.
If anyone is interested … if might be good to go back to Post #1 and see what this subject matter is about. Yea, it’s in Open Chat, but the drift is now horrendous. It’s as if I’m back in the Usenet days when folks were trolling
Because the only people represented here are those whose first language is English. All right then. Forget it. If you don’t want to understand it.
Well, that’s that then. (Dann ist eben Hopfen und Malz verloren.)
Thank’s for your message
Usenet is alive and still kicking
The problem IMHO is expectations vs reality, we are now over two years when Leap 16.0 development started, so much water under the bridge, announcements, testing, bugs etc, I have systems up and running for almost a year without any major issues, no migrations though, as indicated from the get go, migration was not the plan…
This will be my last message
I had the curiosity to ask the AI and one of the answers was used Webmin
but it’s true, I remember trying Webmin a long time ago at the beginning, but as for the cockpit to date, it wasn’t worth Yast
so I loaded webmin
and yes, there is everything missing from the cockpit, especially the management of Bind, Apache, etc., etc.
so, but it’s a recurring question for at least 25 years Why do you want to reinvent warm water? Why have your own tool when it exists elsewhere?
So I’ll take webmin if needed.
Good to read that Webmin meets your needs.
That is really the question that should have been asked from the beginning: “How do I manage Apache, BIND, and other services on Leap 16.1 now that the old YaST modules are gone?” Instead, the thread started with sweeping statements that Cockpit “doesn’t do 10% of what YaST did” and that “SUSE should not dare to put this OS online.”
Generalised complaints are far less useful than explaining the specific functionality you’re looking for. Once you’ve identified the actual requirement, the appropriate tool/method is usually easy to recommend.
Your premise is flawed. You’re assuming every YaST module should have a Cockpit equivalent. In reality, many of those modules no longer need a distribution specific front end because they have become obsolete, or their functionality is fulfilled by other relevant upstream tools which are better at the job.