Making Grist easier to self-host

I’m working on “Grist Omnibus”, a single docker image that packages Grist together with everything needed to put it on a public server, in the hope that it’ll make life easier for self-hosters. There are so many ways to do authentication, often needing quite fiddly configuration. Setting up certificates for https traffic can also be pretty daunting if you haven’t done it before. Grist Omnibus tries to take care of all that.

I’d be interested in feedback from any self-hosters willing to try it out:

The risk in trying to package something all-in-one like this is that it may not be flexible enough for what people really need, and stretching it would make it complex and defeat the purpose :slight_smile:

Thanks for checking it out!

9 Likes

Thank you, this is a very important work to promote Grist.
And as usual, a few questions:

  1. Will it support team sites out of the box?
  2. Will user management be done in the Grist UI and, as a result, user management in the Grist REST API?
  3. Fine-tuning the installation if Traefik is not used (if installed on Synology, it have its own Reverse Proxy and SSL Certificate Manager)?
  4. Where is user data stored in dex way? Should we prepare to move to dex if we continue to use grist-core?
  5. Support for scaling during further operation (I think this is a privilege of the EE version)?

No, I focused on a single-team setup for omnibus since it is easier to configure.

Omnibus doesn’t change anything about Grist, it just packages it with some other compatible services. If you look at https://github.com/gristlabs/grist-omnibus, you’ll see there’s really not much to it, it is just a few files.

I’d recommending setting the omnibus HTTPS variable to external in that case. You can find details in the README.

You can read about Dex storage options on their documentation. I have it configured to use Sqlite by default. No there’s no particular reason to move to Dex, it is just one way among many to handle authentication. I used if for the omnibus because it was particularly neatly self-contained.

My main goal is to have a good solution to point to for someone getting going with Grist, if they are stumbling on authentication and certificates and the like. As someone who has used Grist for a while, I don’t think it changes anything for you - except that it might help you recommend Grist to someone else if you’re confident they’ll be able to install it :slight_smile:

SSL would just be the ingress on the chart?