What's coming in Cloudron 7.1

[girish]

We are going to spend pretty much rest of the year in packaging new apps. We started on this already - Directus 9, Chatwoot, Redash 10, Baserow are some of the apps we published just last couple of weeks.

For 7.1, we hope to implement:

• Mail manager role
• Password reveal for password fields (this already shipped as part of 7.0.4).
• Multi-domain support for apps like minio, mailtrain v2
• Whatever jitsi needs
• Option to expose LDAP server publicly
• Add LDAP option to expose groups.
• Import/export of users and mailboxes with csv/json
• Add a per-app mail from validation flag (currently, it's per domain).
• IPv6 support

[girish]

Password reveal:

[privsec]

@girish said in What's coming in Cloudron 7.1:

Whatever jitsi needs

This is the coolest thing I have read all week.

@girish you and your team do amazing work and I can never thank you enough.

[A Former User]

@girish said in What's coming in Cloudron 7.1:

• Whatever jitsi needs

This might just be the greatest changelog item I’ve ever seen.

[jdaviescoates]

@girish said in What's coming in Cloudron 7.1:

We are going to spend pretty much rest of the year in packaging new apps.

Nice one.

Hopefully some of the existing apps can be improved too, eg like adding LDAP to Discourse? I really want this, so fingers and toes crossed!

(and, far less important, but would also be nice to have it for Calibre Web too - at present you can actually already choose to use it for that, but it doesn't actually work)

Another +100 on the Jitsi front too!

[girish]

@jdaviescoates said in What's coming in Cloudron 7.1:

Hopefully some of the existing apps can be improved too, eg like adding LDAP to Discourse? I really want this, so fingers and toes crossed!

I think the difficulty here is there is no existing Discourse LDAP plugin . The existing one still does not auto-create users in Discourse after LDAP login, last I checked. Would be some work for us to learn ruby/rails/discourse plugins and maintain this. If someone here or somewhere else, can come up with the plugin, we can integrate it into the package.

[jdaviescoates]

@girish said in What's coming in Cloudron 7.1:

The existing one still does not auto-create users in Discourse after LDAP login, last I checked.

This would seem to suggest that might've been fixed:

https://meta.discourse.org/t/version-2-4-0-beta7-broken-ldap-account-creation/134430/5?u=jdaviescoates

Although the plugin hasn't been updated in quite a while now too, so perhaps it broke again or something

https://github.com/jonmbake/discourse-ldap-auth

Saying that, whilst this issue is still open, it sounds to me like auto creation should work:

https://github.com/jonmbake/discourse-ldap-auth/issues/51#issuecomment-707395562

[girish]

@jdaviescoates Indeed, https://github.com/jonmbake/discourse-ldap-auth#a-note-on-user-account-creation suggests that it does auto create. I will try it and check.

[LoudLemur]

@privsec said in What's coming in Cloudron 7.1:

@girish said in What's coming in Cloudron 7.1:

Whatever jitsi needs

This is the coolest thing I have read all week.

@girish you and your team do amazing work and I can never thank you enough.

Absolutely! Thank you so much for opening up the frontier of Free Software!

[chris]

@girish said in What's coming in Cloudron 7.1:

rest of the year in packaging new apps

yes please, APPS!

And the apps of most interest to me: cal, PhotoPrism , supabase, OpenMemex, Odoo, Listmonk, twake, Chaskiq, GrowthBook, Stackstorm, suitecrm, boringproxy, grafana-loki

[ei8fdb]

@privsec said in What's coming in Cloudron 7.1:

@girish said in What's coming in Cloudron 7.1:

Whatever jitsi needs

This is the coolest thing I have read all week.

@girish you and your team do amazing work and I can never thank you enough.

I also wanted to say thank you for your development work.

I don't have enough time to post in the forums but I appreciate, on a daily basis, the work you all do on Cloudron.

I am regularly (pleasantly) surprised when I see my server has been updated to the next verison, without issues. This is a testament to your great work.

[dylightful]

@girish Wireguard?

[girish]

@dylightful yup, it's high on the list!

[girish]

Mail manager role is now implemented. There is a new role:

That user can then manage mailboxes and users. This role does not allow user to update email service status and outbound settings. Only admin can do those.

[bubonicfred]

@jdaviescoates Yeh, I'd really like to trial an internal forum, but lack of LDAP is blocking that.
Also discourse seems to use an unreal about of resources when running.

[humptydumpty]

@bubonicfred flarum would be nice to have on here

[chris]

@girish so I can stop checking the new apps tab every day, any eta on when new apps will start to be published ?

@chris said in What's coming in Cloudron 7.1:

@girish said in What's coming in Cloudron 7.1:

rest of the year in packaging new apps

yes please, APPS!

And the apps of most interest to me: cal, PhotoPrism , supabase, OpenMemex, Odoo, Listmonk, twake, Chaskiq, GrowthBook, Stackstorm, suitecrm

[girish]

@chris Usually, we put them in the announce category - https://forum.cloudron.io/category/1/announcements . Right now, we are trying to get some of our existing apps up to speed since they require some platform changes (like minio, mailtrain, discourse, gitlab).

[chris]

@girish said in What's coming in Cloudron 7.1:

We are going to spend pretty much rest of the year in packaging new apps

@girish end of the year is upon us, any chance the focus on "packing new apps" by end of year still a thing or did this get delayed? (if delayed, any eta?)

[girish]

It's now possible to expose the LDAP server:

[girish]

Some apps refuse to log to stdout/stderr or are very hard to configure. We have added a new manifest property called logPaths where the package specify an array of log file names - https://docs.cloudron.io/packaging/manifest/#logpaths . This way users don't need to open a web terminal and find the log files inside the container.

[nebulon]

We have added CIFS/samba seal encryption support https://manpages.debian.org/testing/cifs-utils/mount.cifs.8.en.html#seal

SMB v3 on the storage server is required. Hetzner storage boxes support this by now.

[fbartels]

@girish said in What's coming in Cloudron 7.1:

This way users don't need to open a web terminal and find the log files inside the container

Which means that now the admin/operator of an app has a button in the settings of an app to open the files specified in the manifest?

[girish]

@fbartels said in What's coming in Cloudron 7.1:

Which means that now the admin/operator of an app has a button in the settings of an app to open the files specified in the manifest?

It's tailored for logging at this point. When you open log window, it will tail -f those files in addition to stdout/stderr. Though, your idea of having "bookmarks" might be a good idea for a File manager as well.

[fbartels]

@girish said in What's coming in Cloudron 7.1:

will tail -f those files in addition to stdout/stderr.

Ah yes, that makes absolute sense. For a not Cloudron related project I am currently building a container that outputs its main logging to the container and then writes some more verbose stuff (webserver access logging and mail.log) into files. Here such "bookmarks" would be useful.

[girish]

multiple domain support for apps is implemented by httpPorts.

The new minio uses this feature to ask for the api domain separately now at install time:

As always, you can change these in the Location view:

At some point, mailtrain v2, cryptpad (?) etc can use the above feature.

[A Former User]

@girish Oh wow! I could see this with https://appwrite.io too. Exciting!

[jdaviescoates]

@girish said in What's coming in Cloudron 7.1:

mailtrain v2, cryptpad

Both of those would be great!

[chris]

@girish can you please comment ?
@chris said in What's coming in Cloudron 7.1:

@girish said in What's coming in Cloudron 7.1:

We are going to spend pretty much rest of the year in packaging new apps

@girish end of the year is upon us, any chance the focus on "packing new apps" by end of year still a thing or did this get delayed? (if delayed, any eta?)

[A Former User]

@chris Reminds me of people who ask a question somewhere and consistently post with "bump". Its a 2 person team chill out.

[chris]

Hi @atridad, yes i remember those days where we would BUMP things to the top, and I know to @girish and @nebulon are hard at work, prioritizing effort as they can.. and thanks for your hard work and contribution to the community too. I enjoy cloudron and happy to be a long time supporter... This is in fact a bump, about a lingering question- so you're perspective!

[nebulon]

We also added user import/export as well as mailbox import/export. This is mostly for faster onboarding of larger user and mailbox sets. The mailbox import is not actually importing the emails, but creates and associates the email addresses to users.

[girish]

@chris I guess you are asking what new apps are being worked on? We fixed up Redash 10. Then, we updated MinIO, which is an existing app but required much work to keep it updated to latest version since it requires multiple domains now. Recently, we published Paperless-ng. Mautic 4 is being fixed to the latest version.

I understand the response is probably not exciting but our priority is always to keep existing apps updated first before we move on to new ones. Top of our new app list (that is what we are packaging) is Jitsi though, we are fixing the platform first so that it can work well. nocodb and drone is one some states of "done", so we will push that out soonish.

[girish]

We were hoping to get it out this week but looks like it will be the next.

Sadly, we got sidetracked by a bunch of things. Most importantly, we had to remove 'colors' and 'request' module in all our code. Not just box code, but also our CI, appstore etc. Much rewriting with no real end user benefit. Necessary evil Anyway, moving forward, we have decided to use npm as little as possible. We will weigh in the cost of "copy/paste" into our own codebase vs using an external module.

[bubonicfred]

@girish Feel your pain about npm. Was there something new that came up about request? I don't use it directly but use dependencies that do.

[girish]

Final update before the release. Initial, IPv6 support is in - all the DNS backends have been updated to support AAAA records. There is a checkbox in the Network view to enable the IPv6 support.

This is currently "experimental". Currently, there is a lot of complications and unknowns wrt docker's ipv6 support. I will make a separate post about this, but for Cloudron, the initial iteration the plan is to enable IPv6 only for HTTP(S) services. Essentially, the apps will have IPv6 support but not any exposed ports (like say the git port) nor the email server.

[timconsidine]

@girish just wondering about current status of 7.1.0
I needed to move my server and noticed that default install on clean machine is 7.1.0. But in Cloudron it says this release is beta.

I actually installed 7.0.4 on the clean machine, so I could restore from backups. Generally went fine. I then upgraded to 7.1.0 through console.

Seems ok but email status check seems off still.
And System Info shows no data.

[timconsidine]

@timconsidine ah but actually all apps seem stuck in Configuring queued status.

EDIT (1) : they seem progressively to exit this status and become Running

EDIT (2) : System Info now showing some data. But interestingly it seems server was down for a while after upgrade to 7.1 from this chart.

EDIT (3) : 2 apps refuse to enter Running, stuck in Starting ...
They're not critical for now.

So just wondering about 7.1.0

[girish]

7.1 was staged for installation a couple of days back. I would wait before updating though, there is atleast one issue we know of which is now fixed and there will be a 7.1.1. I would not trigger an update on existing installations unless it's not critical (and of course, help us with the testing).

[girish]

@girish said in What's coming in Cloudron 7.1:

Final update before the release. Initial, IPv6 support is in - all the DNS backends have been updated to support AAAA records. There is a checkbox in the Network view to enable the IPv6 support.

This is currently "experimental". Currently, there is a lot of complications and unknowns wrt docker's ipv6 support. I will make a separate post about this, but for Cloudron, the initial iteration the plan is to enable IPv6 only for HTTP(S) services. Essentially, the apps will have IPv6 support but not any exposed ports (like say the git port) nor the email server.

We figured this one out and IPv6 support will be complete in 7.1. It will support export ports and the email server from the get-go! But as mentioned in previous comment, please hold on before updating if your Cloudron instance is critical.

[girish]

@timconsidine said in What's coming in Cloudron 7.1:

@timconsidine ah but actually all apps seem stuck in Configuring queued status.

EDIT (1) : they seem progressively to exit this status and become Running

This is expected. Docker is updated, the internal network is now IPv6 and all app containers are re-created to support IPv6.

EDIT (3) : 2 apps refuse to enter Running, stuck in Starting ...

Can you please tell me which apps these are and what you see in their logs? Sometimes, depending on your server, it could be that they are taking some time to start up.

[timconsidine]

@girish said in What's coming in Cloudron 7.1:

@timconsidine said in What's coming in Cloudron 7.1:

@timconsidine ah but actually all apps seem stuck in Configuring queued status.

EDIT (1) : they seem progressively to exit this status and become Running

This is expected. Docker is updated, the internal network is now IPv6 and all app containers are re-created to support IPv6.

EDIT (3) : 2 apps refuse to enter Running, stuck in Starting ...

Can you please tell me which apps these are and what you see in their logs? Sometimes, depending on your server, it could be that they are taking some time to start up.

Thank you for the offer.
When I reviewed them, I found they were custom package apps.
And I decided I wasn't using them enough, so uninstalled them. Quick solution

[nebulon]

@timconsidine possibly they were using CloudronManifest version 1, which was deprecated for some time now and got removed with 7.1
What this means is, that the injected env vars will now always be prefixed with CLOUDRON_ and maybe your custom apps were still looking for example for MYSQL_HOST instead of CLOUDRON_MYSQL_HOST?

[timconsidine]

@nebulon ah good point, thank you
I will check some other custom apps

[msbt]

@nebulon I still have 2 custom apps running on manifestversion 1, what will happen to them if I upgrade before updating those apps?

[humptydumpty]

@girish said in What's coming in Cloudron 7.1:

7.1 was staged for installation a couple of days back. I would wait before updating though, there is atleast one issue we know of which is now fixed and there will be a 7.1.1. I would not trigger an update on existing installations unless it's not critical (and of course, help us with the testing).

I triggered a manual update check before coming across this post. Is there a way to tell cloudron to skip this update or stop it from auto-updating?

[msbt]

@humptydumpty go to Settings and change the update schedule, in there you can choose to disable automated updates

[avatar1024]

@humptydumpty I believe that updating to 7.1 can only be done manually and will NOT happen through auto update (if with auto update enabled).

[nebulon]

@avatar1024 that is correct, releases which are not yet put out for all users, will not be auto-updated. Our current approach is, to first make a release for new installation and people who would like to manually update to it. Then if things look good, we will slowly roll it out for auto-updates (if enabled on a Cloudron) over around a week or so.

[girish]

@msbt manifest v1 apps won't work anymore in 7.1. i.e it will just not start properly. Note that just bumping the manifestVersion to 2 and changing the env variables to CLOUDRON_ is all that is needed, nothing else.

[imc67]

@girish said in What's coming in Cloudron 7.1:

@girish said in What's coming in Cloudron 7.1:

Final update before the release. Initial, IPv6 support is in - all the DNS backends have been updated to support AAAA records. There is a checkbox in the Network view to enable the IPv6 support.

This is currently "experimental". Currently, there is a lot of complications and unknowns wrt docker's ipv6 support. I will make a separate post about this, but for Cloudron, the initial iteration the plan is to enable IPv6 only for HTTP(S) services. Essentially, the apps will have IPv6 support but not any exposed ports (like say the git port) nor the email server.

We figured this one out and IPv6 support will be complete in 7.1. It will support export ports and the email server from the get-go! But as mentioned in previous comment, please hold on before updating if your Cloudron instance is critical.

Just updated to 7.1.2 I noticed I had to 'save location' of the apps to add the AAAA records. However the mailserver and Cloudron access URL still don't have AAAA records, not even after restarting the mailserver. Is this expected?

[girish]

@imc67 you have to go to Domains -> Sync DNS records for the existing apps/mail server.

Before you suggest it, yes, we should probably do this when IPv6 is enabled As a heads up, there is also a quirk that if you disable IPv6, the AAAA records are not removed by the sync .

[micmc]

@girish said in What's coming in Cloudron 7.1:

@girish said in What's coming in Cloudron 7.1:

We figured this one out and IPv6 support will be complete in 7.1. It will support export ports and the email server from the get-go! But as mentioned in previous comment, please hold on before updating if your Cloudron instance is critical.

AMAZING WORK! From our exceptional professional and cutting edge team of developers at Cloudron, should it be said once in a while.

Thanks for your fantastic work @girish @nebulon guys you are simply the bests.

[girish]

Cloudron 7.1 is now available to all. Locking this thread.