Support creating a local JupyterLite deployment with git2cpp built from the local repo #36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a new directory
lite-deploycontaining eveything required to build the localgit2cppsource code as anEmscripten-forge package and create a local JupyterLite deployment that can run it in a terminal.
There are comprehensive instructions in
lite-deploy/README.md. Essentially you create a newmicromambaenvironment containing all the dependencies, usemaketo build everything and thenmake serveto serve the web site so that you can view it in a browser. If you change thegit2cppsource code you can rebuild what is required usingmake rebuild.The intention is that will be useful for developers working on PRs to easily see if their changes work in the JupyterLite terminal or not. I intend follow-on work to use this on demand in CI also, perhaps to deploy to Github Pages.
I will need to make new
cockleand/orterminalreleases next week so that we are using the latest code there, for example the changes that have added tococklebut not released yet to support identifying if coloured output is supported or not.