What's coming in 7.2

[girish]

We will be deploying a sign up flow at cloudron.io soon. This requires a new release on the Cloudron side. So, not many features here.

What’s coming in 7.2

• Auto-provision license from cloudron.io. This will create another flow for users to get started with Cloudron - one can sign up at cloudron.io and just run a command listed there to be auto-provisioned with cloudron license. The current install flow will remain.
• Give backups a name and control how they are preserved/cleaned up.
• Rework the backup code to use async/await
• support: add a separate system user named cloudron-support for remote access. With this one doesn't need to enable ssh access for root.
• Unify the app data and volumes code/ui

We also seem to have already accumulated some important fixes:

• mail: hide log button for non-superadmins
• firewall: do not add duplicate ldap redirect rules
• ldap: respond to RootDSE
• nginx: update to 1.20.0-1
• Check if CNAME record exists and remove it if overwrite is set
• cifs: use credentials file for better password support
• installer: rework script to fix DNS resolution issues
• backup cleaner: do not clean if not mounted
• restore: fix sftp private key perms
• sshfs: fix bug where sshfs mounts were generated without unbound dependancy

[ruihildt]

@girish Regarding the Cloudron-support user, what would be the flow when asking for support? User is deactivated by default and enabled? Will it be password based or token?

[girish]

@ruihildt said in What's coming in 7.2:

@girish Regarding the Cloudron-support user, what would be the flow when asking for support? User is deactivated by default and enabled? Will it be password based or token?

The flow for the user remains the same - you just have to go to Support -> Enable Remote Access.

Internally, what this used to do was to add or remove our ssh key into /root/.ssh/authorized_keys. On our side, we used to ssh -i <private_key> root@ip. With this change, the keys will be added into the cloudron-support user. So, in /home/cloudron-support/.ssh/authorized_keys. We will use ssh -i <private_key> cloudron-support@ip instead. The cloudron-support user is also added in sudoers so that we can get root access once we SSH'ed in.

No password based access, only based on ssh keys like before. So, sshd_config can have PasswordAuthentication no

[d19dotca]

Newbie question here for backups… does the async/await make the performance improve significantly for backup times to backends like Wasabi or does it apply more to local backups to external block storage disks and stuff like that? Curious I guess of the real-world impact from that change. Fingers crossed for improved backup times.

[nebulon]

@d19dotca the async/await change mostly does not change performance. This is merely a change to use more modern Javascript features and overall improve code-readability. The previous "callback" style was already async as well.

[girish]

7.2.0 is published for new installs. Highly recommend existing installation to not upgrade. Existing installations won't auto-upgrade (yet), so all you have to do is to not explicitly upgrade.

We made the release since we have to make a cloudron.io release as well to get the new sign up flow going.

[infogulch]

This also includes the proxyAuth change that allows Firefly iii to authenticate again, correct?

[girish]

@infogulch yes! I already pushed out the Firefly-III update, in case you want to test that.