-
-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added Binder setup files #1603
Added Binder setup files #1603
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
Probably best to include download of sample data into the notebook if needed...
Then the commented code at the bottom of the postBuild script could be removed...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you. I think this will be very helpful.
Or download the data always? We don't know how this will be used, so maybe the download on demand in the notebook is best now. Definitively remove the comment. |
|
This is for a separate PR, but I think a GitHub Action should generate a Binder button aka Binder badge (which is just a URL and an image) and post it as a comment to each new PR so that you don't have to guess or construct the Binder URL yourself. That's my idea how this should be eventually used. The URL can also point to a specific notebook so you don't need to go through the directory structure to find it. The button/badge for this PR with notebooks and JupyterLab instead of a plain notebook: Suggestions about the content of the notebook are welcome (there can be also more than one), but that's also for another PR. Empty one is fine with me now as well as skipping the dataset download. |
Yes, I think both ways of handling that would be good. My thought was to have a blank setup and add (sample) data - including location / mapset setup - in the respective example notebook... As allways there are pros and cons and I am fine with either solution... |
Sounds like a very good idea. |
So something like along this line I guess: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can merge after you accept and test the changes.
BTW, perhaps obvious, but I used the button/link to test this and come up with the suggestion.
Co-authored-by: Vaclav Petras <wenzeslaus@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The grass (or !grass) command runs in Binder which is what I saw as the goal for this PR.
|
Awesome! Now all PRs can be tested in Binder. One just needs to figure out the URL either by filling out the form at https://mybinder.org or by filling out this template: |
* Setup files for Binder tested with mybinder.org. * Sample data downloaded during the image build on Binder. * Empty notebook included as a placeholder. * JupyterLab used on Binder. * Using standard system setup of GRASS, so grass command works, but anything else needs to be set up.
* Setup files for Binder tested with mybinder.org. * Sample data downloaded during the image build on Binder. * Empty notebook included as a placeholder. * JupyterLab used on Binder. * Using standard system setup of GRASS, so grass command works, but anything else needs to be set up.
* develop: Add Binder setup files (OSGeo#1603)
* Setup files for Binder tested with mybinder.org. * Sample data downloaded during the image build on Binder. * Empty notebook included as a placeholder. * JupyterLab used on Binder. * Using standard system setup of GRASS, so grass command works, but anything else needs to be set up.
* Setup files for Binder tested with mybinder.org. * Sample data downloaded during the image build on Binder. * Empty notebook included as a placeholder. * JupyterLab used on Binder. * Using standard system setup of GRASS, so grass command works, but anything else needs to be set up.
I'm just opening this pull request draft to get the ball rolling for my Google Summer of Code project. As part of the GRASS and Jupyter Notebook project, we discussed adding setup files to run binder.