4 Commits (main)

Author	SHA1	Message	Date
Paul Fitzpatrick	2be130032e	bump pyodide version number (#735) ... Pyodide packages needed rebuilding, and the pyodide project has moved on a bit so a new version number is needed. The new packages have already been built and pushed to S3. To verify, go to `sandbox/pyodide` and follow the README there. Then at top level do `GRIST_SANDBOX_FLAVOR=pyodide`. Try to create and edit a document using formulas. It should work.	7 months ago
Paul Fitzpatrick	a18007ae7a	remove cached packages for pyodide when cleaning up (#650) ... If these get messed up, it is hard to track down the problem.	10 months ago
Paul Fitzpatrick	5119ce92cb	add a version number to precompiled pyodide resources (#607)	10 months ago
Paul Fitzpatrick	66643a5e6b	add a pyodide-based "sandbox" flavor (#437) ... This adds a new `GRIST_SANDBOX_FLAVOR=pyodide` option where the version of Python used for the data engine is wasm, and so can be run by node like the rest of the back end. It still runs as a separate process. There are a few small version changes made to packages to avoid various awkwardnesses present in the current versions. All existing tests pass. This is very experimental. To use, you'll need something with a bash shell and make. First do: ``` cd sandbox/pyodide make setup # README.md and Makefile have details cd .. ``` Then running Grist as: ``` GRIST_SANDBOX_FLAVOR=pyodide yarn start ``` should work. Adding a formula with content: ``` import sys; return sys.version ``` should return a different Python version than other sandboxes. The motivation for this work is to have a form of sandboxing that will work on Windows for Grist Electron (for Linux we have gvisor/runsc, for Mac we have sandbox-exec, but I haven't found anything comparable for Windows). It also brings a back-end-free version of Grist a bit closer, for use-cases where that would make sense - such as serving a report (in the form of a Grist document) on a static site.	1 year ago