gristlabs_grist-core

Commit Graph

Author	SHA1	Message	Date
Paul Fitzpatrick	5119ce92cb	add a version number to precompiled pyodide resources (#607 )	11 months ago
Alex Hall	d72f177be0	Upgrade to Pyodide 0.23.4 (with Python 3.11) and compile dependencies (#603 ) * Build packages with latest pyodide, compile wheels to use pyc files, output package_filenames.json	11 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

Author

SHA1

Message

Date

Paul Fitzpatrick

5119ce92cb

add a version number to precompiled pyodide resources (#607 )

Alex Hall

d72f177be0

Upgrade to Pyodide 0.23.4 (with Python 3.11) and compile dependencies (#603 )

* Build packages with latest pyodide, compile wheels to use pyc files, output package_filenames.json

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.

3 Commits (cf6579dffad184a83b23b143d46fe95449a624b5)