gristlabs_grist-core/sandbox/pyodide/setup.sh

#!/bin/bash

set -e

echo ""
echo "###############################################################"
echo "## Get pyodide node package"

if [[ ! -e _build/worker ]]; then
  mkdir -p _build/worker
  cd _build/worker
  yarn init --yes
  yarn add pyodide@0.23.4
  cd ../..
fi
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. 2023-03-06 21:56:25 +00:00			`#!/bin/bash`

			`set -e`

			`echo ""`
			`echo "###############################################################"`
			`echo "## Get pyodide node package"`

			`if [[ ! -e _build/worker ]]; then`
			`mkdir -p _build/worker`
			`cd _build/worker`
			`yarn init --yes`
Install pyodide 0.23.4 2023-08-02 11:03:22 +00:00			`yarn add pyodide@0.23.4`
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. 2023-03-06 21:56:25 +00:00			`cd ../..`
			`fi`