Thoughts on how to run iJavaScript on mybinder?
@n-riesco - might you know what would be needed for a notebook to run in mybinder.org - so it would have the ijavaScript kernel running?
Sorry if there are a number of threads on this topic, and I'm adding to them
but I couldn't tell if this still needed something and was open like #196,
or well understood by others, and not me yet like #277 or #188
I've been looking briefly into the documentation, from the great zero-to-binder tutorial
and found in their readme that they support things outside of just requirements.txt - pointing to docs on repo2docker
There it seems like there might be two options:
- Provide a docker file
- Or do something like an
apt.txtto install node and then run apostBuild
I noticed that there was a pull request #192 that seemed accepted (test/ijavascript-base-notebook-latest/Dockerfile) but then removed.
(...although it seems there is a ... copy stored in a gist)
I was curious what the current thoughts were, or if there was an image on dockerhub I missed
For anyone else looking to run your project on mybinder, I made an instance that fixes a few of the issues I noticed with https://hub.docker.com/r/datainpoint/ijavascript-notebook
Writeup is here: https://github.com/paulroth3d/docker_jupyter-ijavascript-utils
TLDR:
Either make a DockerFile similar to the following:
# syntax=docker/dockerfile:1
FROM darkbluestudios/jupyter-ijavascript-utils:amd_1.0.1
Or, if you'd like to update to have your own npm modules pre-installed:
- make your own Docker image, adding in
package.jsonandpackage-lock.json - Create a
Dockerfileand look at thisDockerfilefor what was used there
@n-riesco - would rather ask - would this be okay to close?
I also put a comment on #196
as it seems like some work has been done there a bit, if you'd like to put in a comment there too.
@paulroth3d First of all, apologies for my silence (I keep forgetting about open issues like yours, when I can't act on them right away :disappointed: ).
I've labelled this issue as a question (I'm using this label as temporary FAQ before I rehaul the README).
Thank you for all the work you've put. It looks impressive in many ways. I want to give it more visibility in the README (I will leave this issue open as a reminder for me to do so).