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.
I'm submitting this PR not expecting it to get merged as-is, but as a strawman for discussion. It contains:
minimal-notebook
which acts as a base image or a lightweight notebook environment in which the user can use conda to install everythingscipy-notebook
for a Python 2 and 3 stackr-notebook
for an R stackMost package versions are pegged to allow patch level increases only to avoid breakage across Docker builds. (I've learned this the hard way.)
If this is inline with what people are thinking for this repo, follow-ons might be:
all-spark-notebook
(Scala, Python, R w/ Spark 1.4.x plus Yarn and Mesos connectivity preconfigured)data-science-notebook
(needs a better name) with Python, R, Julia, Scala, Spark (Brian's request)julia-notebook
maybeI don't want to go too crazy with a ton of different options yet until we know if less is more or not.
Ideally, once these (or alternatives) are merged, the jupyter account on Docker Hub can be configured to build the minimal-notebook stack on commit and webhook build the other stacks on build of that base.