![]() Jupyter Notebook can be easily published as web application thanks to Mercury framework. My repository is available at /pplonski/share-jupyter-notebook. Let’s start a new GitHub repository (it is rather a good idea to keep code in repo). The last step will be deployment of the interactive notebook to the cloud (with Heroku). ![]() Then, I will add YAML header to make a web app from notebook with Mercury framework. First, I will create an example notebook. I will go step-by-step process of how to make a Python notebook accessable for non-technical users. What to do? Don’t worry! In this post, I will show you how to share Jupyter Notebook with non-programmers. This can be tedious manual work that might require many updates if data and final results will changes. Your peers don’t understand Python and can’t reproduce your work on their own computers. How to do this? You can’t send them the ipynb file in the email attachement or just push it to the GitHub repository. Congratulations! What’s next? You need to share your Jupyter Notebook with non-programmers. You can combine it with ReviewNB to remove some of the kinks in the workflow.Your analysis is ready. But it’s a proven way of collaborating on software projects & is widely used in data science work as well. If you are new to Git, it can take some time to get used to all the commands. You can use nbviewer or ReviewNB if your notebook contains interactive widgets and such. If it’s a private repository, the person you are sharing the link with needs to have a GitHub account and have permission to access your repository.įor security reasons, GitHub does not run any Javascript in the notebook. So it’s very convenient to share read-only links to the notebook like this one. When you browse notebooks in your repository on GitHub it renders them as HTML. Open the desired commit and click “View File” to see the notebook status at that commit. You can also browse old commits on GitHub by going to Your project page -> Commits. If you want to actually revert to an old state and make some changes there, you can start a new branch from that commit. At the end run “git checkout master” to go back to the current state. If you want to temporarily go back to a commit, checkout the files, and come back to where you are then you can simply checkout the desired commit. Or run git merge + git push from command line, Once your changes are approved you can merge them from GitHub UI. It shows you rich diffs & lets you comment on any notebook cell to discuss changes with your team. You can use ReviewNB to solve the notebook diff’ing problem. But in the case of Jupyter, GitHub shows JSON diffs which are really hard to read (see below). GitHub pull requests are fantastic for peer review as they let you see changes side-by-side & comment on them. On the next page provide title, describe your changes in brief & click “Create pull request” again. Go to your Project page -> Pull requests tab -> click “New pull request”.Ĭhoose which branch you’d like to merge into master. You can create pull requests from GitHub UI. Most likely, you’d want to first share it with your peers, get their feedback before merging it into master branch. Let’s say you’ve been working on feature branch for a while, and it’s ready for prime time. > git push -set-upstream origin customer_data_insightsĪnd then do git push to push your commits to this newly created branch. Setup your name & email in git by running following commands on terminal
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |