|
1 | 1 | # Gerlich Jupyter |
2 | | -**Gerlich Jupyter** This is the the Gerlich group base container for [JupyterHub](https://jupyterhub.vbc.ac.at/), with all internally used NGS and image analysis tools preinstalled. |
| 2 | +**Gerlich Jupyter** This is the Gerlich group base container for [JupyterHub](https://jupyterhub.vbc.ac.at/), with all internally used NGS and image analysis tools preinstalled. |
3 | 3 |
|
4 | 4 | # Startup on VBC JupyterHub |
5 | 5 |
|
6 | | -You can run use this container on [JupyterHub](https://jupyterhub.vbc.ac.at/). |
7 | | -To set it up, use the following settings. |
| 6 | +You can use this container on [JupyterHub](https://jupyterhub.vbc.ac.at/). |
| 7 | +To set it up, use the following settings: |
8 | 8 | - After authenticating on JupyterHub and clicking "Add New Server" on the hub homepage, select `JupyterLab based on custom Singularity image (EXPERIMENTAL)` |
9 | | - - Type in the link to the image location, you can find a link in the [changelog](./changelog.md) |
| 9 | + - Type in the link to the image location. You can find a link in the [changelog](./changelog.md). |
10 | 10 | - **Attention:** You do not need to contact IT. We set everything up for you! |
11 | 11 |
|
12 | | - |
13 | 12 |  |
14 | 13 |
|
15 | | - |
16 | | -You change the version by changing the version identifier, which is the part of the image URL after the colon: |
| 14 | +You can change the version by modifying the version identifier, which is the part of the image URL after the colon: |
17 | 15 | `.../gerlichlab/jupyter-gerlich:YOUR_FAVORITE_VERSION` |
18 | 16 |
|
19 | | -or <span style="color:red">**copy and past the link from the version subsection below.**<span> |
| 17 | +or <span style="color:red">**copy and paste the link from the version subsection below.**<span> |
20 | 18 |
|
21 | | -**Please for now use the cached location!** |
22 | | - |
23 | | -Once the server is started, do not choose a specific kernel. Rather, choose the basic Python3 kernel. |
| 19 | +**Please, for now, use the cached location!** |
24 | 20 |
|
| 21 | +Once the server is started, do not choose a specific kernel. Instead, choose the basic Python3 kernel. |
25 | 22 |
|
26 | 23 |  |
27 | 24 |
|
28 | | - |
29 | 25 | It will contain everything installed in the container. |
30 | 26 |
|
31 | 27 | # Running the notebook locally (OPTIONAL) |
32 | | -For your convenience, you can then start a notebook server with all the necessary libraries installed with: |
| 28 | +For your convenience, you can start a notebook server with all the necessary libraries installed by running: |
33 | 29 | `docker-compose up` from the command line in the directory of this repository. |
34 | | -Then open up a browser and navigate to http://localhost:9999 or http://localhost:9999/lab for the jupyter lab interface. |
35 | | -This will prompt you for a password, which we disclosed in the python club lecture. |
| 30 | +Then open a browser and navigate to http://localhost:9999 or http://localhost:9999/lab for the JupyterLab interface. |
| 31 | +This will prompt you for a password, which we disclosed in the Python Club lecture. |
| 32 | + |
| 33 | +If you use this setup more regularly, please change the password in the `jupyter_notebook_config.py`. |
| 34 | +To do this, modify the following line in the configuration file: |
| 35 | + |
| 36 | +```python |
| 37 | +# The string should be of the form type:salt:hashed-password. |
| 38 | +c.NotebookApp.password = u'sha1:d1ed07fdae18:5423fffeca03b4b1c1d96f79317abe816a220a69' |
| 39 | +``` |
| 40 | + |
| 41 | +To create a new hashed password, you can use the following Python code: |
| 42 | + |
| 43 | +```python |
| 44 | +from notebook.auth import passwd |
| 45 | +print(passwd()) |
| 46 | +``` |
36 | 47 |
|
37 | | -If you use this setup more regularly, please change the password in the jupyter_notebook_config.py |
| 48 | +This will prompt you to enter a new password and generate a hashed password string. Replace the existing value of `c.NotebookApp.password` with the new hashed password string. |
38 | 49 |
|
39 | 50 | # Connecting the local notebook to VSCode |
40 | 51 | A brief description by Michael can be found [here](https://github.com/gerlichlab/python_club_seq_formats_I). |
41 | 52 |
|
42 | 53 | # How do I get a custom version? |
43 | 54 |
|
44 | | -1. Fork the repository |
45 | | -1. Create a new branch |
46 | | -1. Modify the [gerlich_base.yml](./gerlich_base.yml) (e.g., add all your missing libraries or change the version of the libraries) |
47 | | -1. Test your build by running: `docker-compose -f docker-dev.yml up` |
48 | | -1. Test your notebook in the browser: `http://localhost:9999` |
| 55 | +1. Fork the repository. |
| 56 | +1. Create a new branch. |
| 57 | +1. Modify the [gerlich_base.yml](./gerlich_base.yml) (e.g., add all your missing libraries or change the version of the libraries). |
| 58 | +1. Test your build by running: `docker-compose -f docker-dev.yml up`. |
| 59 | +1. Test your notebook in the browser: `http://localhost:9999`. |
49 | 60 | 1. Pushing your branch will create a pull request. Add a description for your version, including what is different from the base version and why it was created. The description can be extended and modified on the GitHub homepage. |
50 | | -1. Contact Christoph or Michael. We will give it a new version number and make it available on JupyterHub, at `jupyterhub.vbc.ac.at` |
| 61 | +1. Contact Christoph or Michael. We will give it a new version number and make it available on JupyterHub at `jupyterhub.vbc.ac.at`. |
0 commit comments