You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 4, 2018. It is now read-only.
I opened this issue on the suggestion of @choldgraf. I asked if should I add the Dockerfile that I prepared for Octave (esp for medical image processing) to the DockerHub, so that other people who'd like to work with Octave on Binderized notebooks can make use of it.
On the other hand, there is this commonly mentioned repo2docker solution, which sounds amazing! I have no experience with it, but if it can make my repos work without the effort that I needed to make my analyses work (it took specifically configured builds etc.), I would call it a magic wand as being a newbie enduser :)
I hope this wraps up the main idea of the topic, strategy for supporting new languages. If not, I am sure @choldgraf will present the arguments those will best ignite the discussion.
Hi All,
I opened this issue on the suggestion of @choldgraf. I asked if should I add the Dockerfile that I prepared for Octave (esp for medical image processing) to the DockerHub, so that other people who'd like to work with Octave on Binderized notebooks can make use of it.
On the other hand, there is this commonly mentioned repo2docker solution, which sounds amazing! I have no experience with it, but if it can make my repos work without the effort that I needed to make my analyses work (it took specifically configured builds etc.), I would call it a magic wand as being a newbie enduser :)
I hope this wraps up the main idea of the topic, strategy for supporting new languages. If not, I am sure @choldgraf will present the arguments those will best ignite the discussion.
All the best!
Agah