How to run the website demo locally?

[not-my-profile]

It seems like Pyodide is currently only built in the GitHub action via a custom docker image.
Is there a way to run this locally? For example if you wanted to improve the demo.

[birkenfeld]

Yeah, there is no good description for that currently. You can probably see from the action that the "magic" all happens in the birkenfeld/pyodide-pygments-builder docker container, which is built from https://github.com/pygments/pyodide-artifacts. This then has to be run with the GITHUB_WORKSPACE variable set properly, but that should be more or less it.

[not-my-profile]

What should GITHUB_WORKSPACE be set to?

[birkenfeld]

If I interpret it correctly, it will be the path where the repository checkout is mounted into the container. The container entrypoint will copy the package from there, build the JS artifacts, and copy it back to pyodide in the checkout root. The workflow then copies that into the Sphinx output under _static.

[Anteru]

Should we keep this open? Do we need to update the docs?

[not-my-profile]

I actually did not manage to get it working with docker and ended up downloading the _static/pyodide/ files from the pygments.github.io repository (which suffices for just testing changes to the demo JavaScript).

I think ideally the Makefile would print some instructions when run with WEBSITE_BUILD=1.