I’m really interested in this because machines with only 2Go RAM (VPS) need to be restarted every 15 days because of some kind of memory leak related to ClamAV.
Could you elaborate in which way those signatures are useless ?
First received a nethserver-subscription module update, After that the version update button.
Before hitting the button for update, I created a snapshot (my subscription server is running on a VPS)
Currently updating. Will report back when the update is finished.
/edit: after 20 minutes, update finished successfully
/edit2: checked all installed services. Running fine!
Well… seems that there are quite a number of issues still under the hood. For 7.7 and Cockpit.
So, “trappolino” for now suits quite better than “tarallino”.
Don’t you think @alefattorini?
But it’s not meant to be evil.
Cockpit and 7.7 are quite rough as a release, both needs a lot of polishing and edge smoothing. Due to necessity of restore-data module, Cockpit is not anymore “an option to play with”, but a necessary tool for day-to-day use.
So it’s given two options for the GUI: NethGUI which work quite well but won’t receive any development and cannot be used for restore, or Cockpit which is showing a lot of things that needs to be fixed by user experience perception.
I think that 7.7 release was a bit early and should have been proposed as “beta”, allowing to end users to decide (upgrade or postpone).
Thats still a bit rude even if your argument are receivable . The fact is that new UI just got out of beta and certainly needs to be polished.
Yet, that’s a real amazing job and there more and more tasks I prefer to do with cockpit and that since the first alpha version.
Maybe we should open a thread dedicated to cockpit UI/UX issues or comments ? I personally get really psycho rigid when it comes to UI, yeah I’m an addict still I want to recognize the job done.
I’m already used to switch from/to old and new UI when needed. that’s probably not ideal but hey, that’s free and really working !
Maybe a link to / from the corresponding module to the other UI could help ? Just a though.
I don’t think so, compared to how many (new) things the new UI does and how much work it required and the short wallclock time (1yr) the devs spent on it.
I know my point of view is biased, but I consider this effort a little miracle
Well done Edoardo and Giacomo! Keep up the good work!