Grist is now available

[Teiluj]

@paulfitz Hi Paul - thanks for stopping by and your helpful pointers.
No doubt that this will be looked at by the Cloudron Team in no time.

Depending on what the @staff thinks, do you think that adding cloudron there could be an option?

Is there any requirements / wishes from you/Grist for this to happen?

Having you here on the forum is most appreciated!

[nebulon]

Hi and welcome @paulfitz! This is a great hint and we will certainly adjust the package to make this possible for your and our users. I am especially happy if this works without having to publish two app flavors for this like some other apps require.

[nebulon]

New app package is out, which prepares the app for enterprise edition usage.

[paulfitz]

Perfect, thanks you @nebulon ! Yes, there's no need for two flavors, there's a toggle in the admin panel. @teiluj I'll look at getting cloudron on that "Get started quickly" list.

[paulfitz]

@teiluj it is listed now

[stbg]

Ahh, fantastic!
A business app
Thank you so much!

[alexis.co]

Hello, I see in the admin panel that pyodide is the sandbox configured for the grist app.
However grist suggest gvisor, but when adding the GRIST_SANDBOX_FLAVOR=gvisor environment variable, and restarting the app, it is still pyodide. Is it on purpose or do I miss something in the configuration ?
Also, I see the app is tagged "unstable", is it more by prevention (as I see the app run well) or really not advised to use it for pro as of now ?
Thank you very much for adding this app to the catalog ! Great job !

[james]

Hello @alexis.co

Currently, Cloudron sets export GRIST_SANDBOX_FLAVOR="pyodide" as default and can not be overwritten.
From a short research I found that pyodide should be used when running inside Docker, what we do.

@alexis.co said in Grist is now available:

Also, I see the app is tagged "unstable", is it more by prevention (as I see the app run well) or really not advised to use it for pro as of now ?

An app being tagged as unstable means that the app is still very fresh and was not yet tested by many users.
We also mark such apps to inform the user, you, that the app might have flaws which could lead to issues when using in a production environment.

[alexis.co]

@james Thank you for the quick feedback !

[paulfitz]

@nebulon said:

New app package is out, which prepares the app for enterprise edition usage.

@nebulon I see that this got reverted. Would you be willing to try again? We moved enterprise material from a repo to a tarball, updated the install:ee script, checked that everything was working, and removed the repo - forgetting that the last packaged version of Grist still expected it. Sorry for the goof. Everything should be good again as of v1.7.13.

[joseph]

@paulfitz yes, we will look into this again. cc @james

[james]

Grist now has enterprise options again.
https://forum.cloudron.io/post/125494

[james]

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.