I discovered Grist a few days ago. I fiddled with it(the web app) and I really like it, it’s great and promising! I checked other alternatives, but to me Grist is clearly the winner(for now at least).
I’d like to use it on my home PC. I will be the only user and I won’t need to use it with Internet. So I won’t need things like login system for example.
My question is : if I build the application from source, is it possible to package it as an ElectronJs app? Is it trivial/easy to do it? Does Grist licensing allow me to do that?
Hi @sitepi7247, welcome! Grist actually started life as a standalone electron app, and I miss that myself, so I’m happy to hear you looking into this! Grist licensing does allow it (everything in https://github.com/gristlabs/grist-core/ is under the Apache-2.0 license). It won’t be trivial. The basic app is in good shape for packaging but a few issues come to mind:
Grist uses python for formulas. A truly standalone ElectronJs app would need to have python embedded within it. If it is just for yourself, you could choose not to worry about it.
There are some node packages with binary components (specifically node-sqlite3), so have an OS-dependent component to deal with. Again, if you are just doing this for yourself, you could choose not to worry about it.
Grist now assumes it controls document creation and storage, it would need some tweaks to be able to save/load Grist documents anywhere on your file system.
You might find it is ok to just run Grist locally with docker. It won’t need the internet, and it’ll have a trivial login system by default.
Wow, good to know! So what made you drop out that option? Is it for the same reasons you mentioned in your post(embedding Python, OS dependency, etc…?)
I will check the docker option, and see if I’m satisfied with it first.
Anyway, thanks for your advice on what to look out for if I go the Electron route. Perhaps I will still try that standalone electron thing…But it looks hard to do based on what you said.
People wanted to be able to try Grist out without installing it first, so we needed the web app. And then it made sense to focus our efforts on making it excellent. I do hope to see Grist packaged in all shapes and forms in the future
I saw your last answer when you posted it last week. For the last couple of days, I’ve been trying to make that docker toolbox work on my win8 computer, to no avail, alas… Docker toolbox successfuly instals, but can’t work. There are different error messages that I tried to solve by googling, but I failed. So yeah, here is where I am. Thanks for your help anyway…
This provide me a first way to ensure data are easily retrievable.
Is it possible to install and run it on a local machine and access it through 192.168.X.X ?
(subcontractor not able to deploy docker on windows it is a nice work_around
Also if running the winpython packed, I think it is possible to install additional python library…
I wasn’t going to post about this yet, since there’s a lot still to do before this is a solid Grist installation, but I got a DM from someone who has been looking for a more recent Electron build of Grist, so I thought I’d give an update. Just to emphasize, this work is unofficial and has a big punchlist of stuff I haven’t gotten to yet.
Thanks a lot for this unofficial release, we are using it internally (since ~6months) on local virtual server.
I’ve sucessfully installed it on W10 pro → Grist-electron as an app is working well, I’ve sucessfully imported .grist file from a small app → No issue
My concern is we cannot access it via a web browser (tested → localhost:8484 | 127.0.0.1:8484 and local IP 192.X.X.X:8484) while we could with Stan release (see above)
I did the same with putting .env with my local IP or 127.0.0.1 (without port) and then pointing on it (eg 192.X.X.X:8484 or 127.0.0.1:8484) → No success.
I’ll make other test on other machine to confirm it.
Anyway thanks again.
Ah, I reused some ancient code that uses port 47478 by default (apparently that was part of Grist Lab’s phone number at some point). And I left the host as local only. I’ll make an update for your use-case. Thanks for trying it out, and glad to hear it works as an app on W10.
Hi @paul-grist, thanks for your work, Electron app is very useful in simple internal/LAN only environment.
But sometime, there will still be some basic view-only needs internally , so I create .env and set GRIST_FORCE_LOGIN=false to make anonymous web access work, but user still can simply click Sign in Button to get owner access.
I’m curious, is there a simple way to disable Sign In UI when anonymous web access using Electron Grist.
@7c9zfztk I don’t think Grist packaged as an Electron app is ready to be used in an environment with different levels of trust.
There is no sandboxing, so an untrusted user who can edit formulas would have access to unrestricted Python running on your machine, and that’s dangerous. I have a plan for adding sandboxing to Linux and Macs, but not yet for Windows (though Windows does offer a brute-force sandbox feature). What operating system are you using?
Connections are plain http and not encrypted https, so network traffic could be readable in transit.
And there’s no login mechanism built in, just a stub. Authenticating nicely works best with some external service. That said, adding new login mechanisms to Grist is fairly easy. What were you imagining? Treating someone who is using the Electron app directly as an owner, and anyone accessing via a browser as an anonymous guest? That could be done.