We are still planning more changes in that version, in particular for the app catalog / install process, and for our dyndns mechanism, but so far the highlights are:
Replace the ‘admin’ user with a new ‘admins’ group. On the long-term, this should remove some confusion about the role of the admin user and allow to define several admin users! Note that this impacts the login screen, as you’ll now have to enter the username in addition to the password! Right after upgrading to 11.1, the old ‘admin’ user will still exist as a regular YunoHost user, member of the admins group. The very first user you created in YunoHost will also be automatically added to the ‘admins’ group and will be able to connect to the webadmin using the same credentials as on the user portal. We recommend to get rid of the legacy ‘admin’ user once you validate that this is okay for you! (To do so, just go to the webadmin > Users > admin > Delete)
Introduce a new “v2” app packaging format. This is in particular a major change for app packagers as it should simplify the app packaging and maintenance, but will also bring many UI/UX improvements for the app install process. On the long term, this is only an intermediate step towards an even-better “v3” format later
Rework the app catalog and app info views, now with logos, screenshots, better descriptions, links to upstream website/doc/demo.
Rework the domain list and domain info view. Domains are now displayed as a tree, and the various panels have been merged into a single one, which should be easier to browse and understand. Behind the scene, we’ve also extended the possibilities of the new configuration panel format introduced in 4.3!
Domain settings to disable mail or XMPP are now effectively reflected in the system configuration instead of just affecting the recommended DNS configuration
Refactor the “global” settings and make them available in the webadmin. So far, these were only available from the command line but they can now be found in the ‘Tools’ section of the webadmin. In particular, those settings allow to harden the security of the server, to configure email relay, and other technical aspects of the server.
A dark theme for the webadmin, much spook! You can enable it in the webadmin settings in the ‘Tools’ section of the webadmin.
And as always, a bunch of minor fixes and improvements for daily life!
How to participate to the beta-testing
DO NOT do this on a critical production server!
From the command line, you can launch the following command to switch to testing:
(If you are familiar with bash scripting, you might want to read what this script does before blindly running the command)
You should then be running YunoHost 11.1.x.
What to test?
Here are some specific items which are important to check to validate the current work:
Validate that you’re indeed able to login to the webadmin following the new ‘admins’ group change. Possibly delete the old ‘admin’ user once you confirm that you’re able to connect with your main user (the very first user that was created on the server).
Test the dark theme !
Test the new domain views and tell us if you find it better than the previous one, and/or if some specific items could be improved.
Test to install / upgrade various apps, especially following the work on packaging v2, we want to make sure that everything stays backward-compatible with v1 apps.
On my side, i had configured a user receiving email from root@ & co onto a separated account dedicated to that we can call here A. So this user A was automatically added to admins group.
However, this configuration doesn’t feet my needs, cause i want to synchronize via IMAP those system emails AND for security reasons, i don’t want an admin password to be configured in an email client.
So the solution i find was to remove this user A from admins group (all member of admins group receive root@ email now) AND i made an email forward from my admin B to my non admin user A.
To do that, i had to check admins group was now configured into LDAP to receive root@ & co. It’s not written in “Manage permissions & groups view”.
Nice job, i will be able to upgrade system in the night
About multi admin, i don’t know if it’s wanted, i got
$ sudo su
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
[sudo] password for ADMIN_USER:
It seems that the update rewrite ssh configuration. My ssh port was XXXX and after update, it come back to 22 but the firewall didn’t open port. I wasn’t able to connect through ssh before opening port 22 on firewall and connect through 22 port.
I also get an error with migrations on the webadmin :
update tell me that there is waiting migration
going to tools->migration give me a 500 error :
Impossible de charger la migration 0025_global_settings_to_configpanel : cannot import name 'translate_legacy_settings_to_configpanel_settings' from 'yunohost.utils.legacy' (/usr/lib/python3/dist-packages/yunohost/utils/legacy.py)
running yunohost tools migration state through the cli give me the following result :
Migration done (a little randomly as I thought I was back in stable).
Everything is working as intended, with just a little graphical problem with the pacman with it’s rough white border.
Everything else is so much BETTER than before (and before was already awesome )
The access to the configuration parameters from the web interface will make things easier and accessible for those who do not read the documentation. Now everything is available and explained, this is awesome !
Thanks a lot to the YunoHost team and NLnet foundation
Yeah these are now handled by the admins group behind the scene … though so far there’s no way to explicitly see them from the webadmin … but oneday™ we’ll implement mail-alias management for groups, which should also solve a bunch of use case and have a minimalist mailing-list mechanism (eg behind able to define contact@).