Jupyter: Simplified instructions by assuming same port on localhost and dev node

[HenrikBengtsson]

If one can assume that the port used on the dev node is available on user's local machine, then one can simplify the instructions on https://wynton.ucsf.edu/hpc/howto/jupyter.html a bit:

• The URL outputted by Jupyter (e.g. http://127.0.0.1:47467/?token=57041544d4cacfdc71c2201d6bebe5b16fcec6bc8397fc98) works as-is in the user's local browser
• There is only one port to focus on when setting up the SSH connection, e.g. ssh alice@dev2.wynton.ucsf.edu -J alice@log2.wynton.ucsf.edu -L 47467:localhost:47467

The downside is that this trick blurs the what's going on with local and remote ports, if there's a port clash. However, the risk for a port clash on localhost is much lower than on the dev nodes.

[HenrikBengtsson]

@ellestad @murashka-ucsf , I think I saw a recent support email where one of you suggested to use:

-L 47467:localhost:47467

instead of

-L 8888:localhost:47467

as suggested on the website (https://wynton.ucsf.edu/hpc/howto/jupyter.html).

I just got a question how to do this from a C4 user, and I think they might miss that they need to tweak the URL that Jupyter outputs so it uses port 8888 instead.

I'm starting to think that using the same localhost port as dev-node port would remove some of the potential potholes, and it would simplify the instructions a big. What do you think?

[HenrikBengtsson]

I've made these updates now. This way, the HTTP links outputted by Jupyter works as-is. No need for the user to edit/modify the URL. This means that most users can click on the link directly in the terminal.

I updated https://wynton.ucsf.edu/hpc/howto/rstudio.html the same way.