Create JupyterLab based version of Dockerfile #347 #356
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 is the start of the jupyterlab interface as requested in issue #347 . It is based on the openworm/openworm docker image, so it contains all required packages including precompiled sibernetic.
It is meant to be used with docker-compose, which is the standard way of making more complex docker workflow (and my suggestion would be to change also other containers in this way). After starting the docker container with
docker-compose up(as described in docker/README.md), the jupyter interface is available on http://localhost:8888To fully comply with the request in the issue #347, it should also include Jupyter notebook with some usage example. However, it fails to finish for me at the moment, so I leave it up to someone more experienced with openworm.