@timconsidine sagte: And the position is still only update to ubuntu 26.04 after cloudron 10.0.4 ? Yes.

Ah so essentially this: https://forum.cloudron.io/topic/1977/platform-data-and-other-disk-usage/26

I looked into years ago for our old stack but with Cloudron providing its own mail store and smtp stack on top of the read-only nature of the app container it was not really a fit. Nowadays our stack is even more "heavyweight" (due to the need to be able to scale to 10.000s of users on a single node) so I don't think it would be a good fit for an app.

Perfect timing. I am looking to replace SoGo and lo and behold, Team Cloudron to the rescue. I will definitely check this out and provide any feedback.

Perfect. Time to check it out! Thanks team.

Thank you and well done!

@nebulon no worries, problem solved.

This is awesome, thank you!

@girish I get it, I am not suggesting making it anything else. A better integrated bookmarking system is it. Simply one that doesn't have to switch tabs or copy paste URLs to version files.

Hello @paulfitz Did something change with updates from 04.06.2026 until now in Grist change regarding the enterprise logic or stuff? In the following thread https://forum.cloudron.io/topic/15602/allow-email we noticed that clicking Switch to Full Grist is no longer working for the Cloudron Grist app. Thus, also the enterprise and email notifications are no longer working. Some change must have created this issue from Grist version 1.7.15 or 1.7.16. Since we only recently added the enterprise option again after it was reinstated with install:ee on 19.05.2026 having it fail on us just after two updates again is rather frustrating. EDIT: I have narrowed down that the issue arises when updating Grist from version 1.7.15 to version 1.7.16. In version 1.7.15. In the changelog of grist 1.7.16 is this statement: yarn install in grist-core now builds the full edition by default, via a post-install hook that downloads the ext material from grist-ee. Use yarn run set-community-edition to skip it (the previous behavior) or yarn run set-full-edition to opt in explicitly. The chosen edition is saved to grist-edition, GRIST_EDITION takes precedence, and GRIST_SKIP_EXT_AUTOSETUP skips the hook for contexts where extensions are installed manually (Docker builds, grist-desktop, grist-static) (commit ) According to that, the default should be full but the Cloudron app defaults to community. Using the admin ui and clicking Switch to Full Grist does nothing after a restart. The edition stays community. Even when setting export GRIST_EDITION=full and restarting the app the edition stays community. Even putting the app in recovery mode to allow full read-write, running yarn run set-full-edition: yarn run set-full-edition yarn run v1.22.22 $ echo full > grist-edition && yarn install [1/4] Resolving packages... warning Resolution field "@gristlabs/sqlite3@6.0.1-grist.1" is incompatible with requested version "@gristlabs/sqlite3@^5.1.4-grist.7" success Already up-to-date. $ buildtools/install_edition.sh + ext already at grist-ee (date-2026-06-29-15-21-09); using cached copy warning package.json: No license field warning No license field [1/4] Resolving packages... success Already up-to-date. + Full edition ready (ext/ and ext/node_modules). Done in 1.38s. creates the grist-edition file cat grist-edition full But still, the UI will not use the full edition and stays community. So neither of the documented ways to set the edition nor the web UI is working for the Cloudron app, even when the app is in recovery mode allowing full read-write access.

Shoutout and thanks to @tronical for the initial package.

The existing 9.2 release got renamed to Cloudron 10 yayyyyy. Given that it brings Ubuntu 26 support and really lots of new stuff, it's worthy of a major bump.

@robi good catch!