Overhaul cookbook workflows around Jupyter Book 2 and BinderHub#167
Overhaul cookbook workflows around Jupyter Book 2 and BinderHub#167agoose77 wants to merge 2 commits into
Conversation
|
Should've checked here, huh. |
brian-rose
left a comment
There was a problem hiding this comment.
I need to spend more time on a deeper dive here, but I really like what I see here so far. I have one specific comment about the hard-coding of the binderhub URL.
| # This action sets up evironment variables for e.g. mystmd to recognise and use | ||
| uses: 2i2c-org/clinder@action-v1 | ||
| with: | ||
| hub-url: https://binder.projectpythia.org/ |
There was a problem hiding this comment.
This is the one place where I think it would be great to avoid hard-coding the solution, in anticipation of more bespoke project-specific binderhubs and/or use of these workflows outside the scope of Project Pythia.
There is a binderhub URL that lives in the myst config as
project:
jupyter:
binder:
url: https://binder.projectpythia.org/
which is actually defined by default in our upstream config file here.
Is there a simple way to parse the myst config to get this URL?
|
I put together a more lightweight revision of the |
Following from the Statement of Work that 2i2c have authored to build out a replacement for BinderBot, this PR sets up the build action to use the https://github.com/2i2c-org/clinder action. It makes the following changes:
myst.yamltags, validated by a schema.mainbranch to GitHub Pages.build.shrecognition for custom builds.The new action simply sets up a BinderHub session and exposes it to the action runner via environment variables (by default). The MyST Document Engine is natively aware of these, and will use them to find the Jupyter Server instead of launching a local one.
I'm testing this over at https://github.com/ProjectPythia/ptype-ml-clinder-test
Note
I had some trouble migrating existing repositories — it seems that most cookbooks are broken in one way, or otherwise need environment variables.