You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A common practice in RStudio is to use an Rproject file on startup, which is given in the --rproj-file argument to rsession, e.g.: rsession --standalone=1 --program-mode=server --www-port=8787 --rproj-file=/etc/foo.rproj
This was a bad idea, suggested to me by an R programmer. On investigation, it turns out that the actual flag is --rsession-config-file arg which just uses arg rather than /etc/rstudio/rsession.conf as the configuration file. But for the JupyterHub use case, the simpler and more reliable solution is just to overwrite /etc/rstudio/rsession.conf in the Jupyter server container image. So this should be closed as unnecessary.
Proposed change
A common practice in RStudio is to use an Rproject file on startup, which is given in the
--rproj-file
argument torsession
, e.g.:rsession --standalone=1 --program-mode=server --www-port=8787 --rproj-file=/etc/foo.rproj
It's no problem to put the rproject file in the Docker container and then add the following lines to https://github.com/jupyterhub/jupyter-rsession-proxy/blob/main/jupyter_rsession_proxy/__init__.py right after line 110:
Alternative options
This might be subsumed (or a special case) of the open PR #86. It appears to have been open for four years without activity.
Who would use this feature?
This is a common way for R users to express startup behavior.
(Optional): Suggest a solution
My proposed solution is in the description above, and I'd be happy to fork the repo, make and test it, and do a PR.
The text was updated successfully, but these errors were encountered: