Repository files navigation

jupyter-rsession-proxy provides Jupyter server and notebook extensions to proxy RStudio.

If you have a JupyterHub deployment, jupyter-rsession-proxy can take advantage of JupyterHub's existing authenticator and spawner to launch RStudio in users' Jupyter environments. You can also run this from within Jupyter.Note thatRStudio Server Pro has more featureful authentication and spawning than the standard version, in the event that you do not want to use Jupyter's.

This extension used to proxy Shiny server as well, however that functionality has beenseparated.

Use condaconda install rstudio ordownload the corresponding package for your platform

Note that rstudio server is needed to work with this extension.

Install the library viapip:

pip install jupyter-rsession-proxy

Or viaconda:

conda install -c conda-forge jupyter-rsession-proxy

rocker/binder contains an example installation which you can run on binder.

This extension launches an RStudio server process from the Jupyter notebook server. This is fine in JupyterHub deployments where user servers are containerized since other users cannot connect to the RStudio server port. In non-containerized JupyterHub deployments, for example on multiuser systems running LocalSpawner or BatchSpawner,this is not secure if Rstudio server is listening on a TCP port. In that case, any user may connect to Rstudio server and run arbitrary code.However, if Rstudio is listening on a unix port, the socket will be protected using unix file permissions. Therefore, we recommend keeping the default configuration, which uses a unix socket and not a TCP port.

The following behavior can be configured with environment variables: