WIP Story #340: Replay Widget on Binder #1
Conversation
This file contains hidden or 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
Author
|
A binder based from this branch is up and running here currently: https://hub.mybinder.org/user/dallinger-ngs2-cycle2-pilot-data-a8sllosu/notebooks/analyses.ipynb |
alecpm
force-pushed
the
stories/340-replay-widget-p3
branch
from
a1c789f to
cf0d4b8
Compare
Story 341: Script/Notebook to collect and replay bot-driven data
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 branch is ready for testing. It uses a Dockerfile to create a Python 3 Jupyter Binder with PostgreSQL and Redis installed. Some initialization code has been added to the notebook to ensure the required services are started since there appears to be no way to have them start automatically with the container.
This implements Scrumdo story 340.
One thing worth noting, the Dockerfile currently pulls in branches of Dallinger and Griduniverse during the build process. Once the docker image is built, creating a binder from the repo will not update the versions of those packages that were pulled into the image. This repo must be updated to force a new image to be built in order to see updates to the underlying python packages.
This should probably not be merged to master until the replay widget branches of Dallinger and Griduniverse are merged to there respective master branches. Currently it depends on the
stories/342-realtime-playbackbranches of Dallinger and Griduniverse