Skip to content

Latest commit

 

History

History
42 lines (31 loc) · 2.23 KB

README.md

File metadata and controls

42 lines (31 loc) · 2.23 KB
Raw

Quepid Jupyterlite Notebooks

This repository contains a Jupyterlite build and some example Jupyter notebooks to be used within Quepid. The build is offline-optimized to be used in environments with no access to the public internet. It prepackages the Pyodide kernel and all dependencies according Jupyterlite manual.

How to

  • The build is Docker based. For a local run try docker run -it --rm -e TARGET_DIR=/dist -v "$(pwd)":/dist $(docker build -q .). This will generate a jupyter-lite-build.tgz with the self-contained Jupyterlite web app in your current directory.
  • On Github a GH action uses the Docker build and is embedded into the build workflow which also add the build artifact as a release asset.
  • To create a new release push a new tag. Then the job will fire.

Updates:

Development

Unzip the TGZ file which will then unpack into ./notebooks.

Run either python -m http.server 8000 --directory ./notebooks or ruby -run -ehttpd ./notebooks -p 8000

Browse to http://localhost:8000 and you should see the Jupyterlite interface.

Development 2

  1. Run docker run -it --rm -e TARGET_DIR=/dist -v "$(pwd)":/dist $(docker build -q .) producing the jupyter-lite-build.tgz.
  2. Unzip it into the ./notebooks
  3. rm -rf public/notebooks in Quepid
  4. Make sure Quepid's docker-compose.override.yml has a line similar to - /Users/epugh/Documents/projects/quepid-jupyterlite/notebooks:/srv/app/public/notebooks 1.bin/docker s for Quepid
  5. In your Browser developer tools under network click "Disable Cache".
  6. Now load the content: http://localhost:3000/notebooks
  7. Make changes,
  8. Do a fresh kernal restart and rerun, the >> button.
  9. Update the footer date stamp.
  10. then download and save the file in ./jupyterlite/files tree.
  11. Delete jupyterlite.tar.gz
  12. run docker run -it --rm -e TARGET_DIR=/dist -v "$(pwd)":/dist $(docker build -q .)