Automatic version detection is done if the default value of auto is used. They can be automatically detected by RStudio Workbench on start up by running the Jupyter command, or can be specified by using the lab-version and notebook-version settings in /etc/rstudio/nf. Due to differences between Jupyter versions, RStudio Workbench needs to know the versions of Jupyter Notebook and Jupyter Lab that are in use. # /etc/rstudio/nf jupyter-exe = /usr/bin/jupyter labs-enabled = 1 notebooks-enabled = 1 session-cull-minutes = 240 default-session-cluster = Kubernetes default-session-container-image = rstudio:jupyter-session Jupyter VersionsĬurrently, RStudio Workbench supports JupyterLab 2.x and 3.x, as well as Jupyter Notebooks 6.x. Sets the -MappingKernelManager.cull_connected Jupyter setting.įor example, your nf file might look like the following: Regardless of this setting, only idle (unused) sessions are culled. Whether or not to cull sessions that have a browser connected. This setting sets the the following Jupyter arguments: -NotebookApp.shutdown_no_activity_timeout= -LapApp.shutdown_no_activity_timeout= To disable automatic shutdown, set the value to 0. The amount of idle time to wait in minutes before a Jupyter session is shut down after its kernels and terminals have been culled. Enabling this sets the following Jupyter arguments: -MappingKernelManager.cull_interval=60 -MappingKernelManager.cull_idle_timeout= The amount of idle time to wait in minutes before a Jupyter session’s kernels and terminals is automatically “culled” (shut down). usr/lib/rstudio-server/bin/jupyter-session-runĮnables/disables running of bash profile scripts when starting Jupyter sessions. It is recommended that you do not change this unless you know what you’re doing, and you need to point to a different script. Path to the Jupyter Session launcher executable/script. The default container image to use when launching a containerized Jupyter session.Ĭomma-delimited list of images that may be used for running Jupyter sessions. The default Job Launcher cluster to use when launching a Jupyter session. List of available Job Launcher clusters for launching Jupyter sessions. It is strongly recommended that you do not change this unless you know what you’re doing! Note that this does not override the default value - if you wish to use some of the default arguments, you must contain the default arguments in the configuration value. Running against multiple different Jupyter versions simultaneously in different Launcher clusters is not supported - they must all be running the same version, or proxying issues will occur.Īrguments to be passed to the Jupyter Notebook command. If Jupyter is being launched via the Launcher and is not installed locally, you are strongly encouraged to set this to the version in use. If set to auto, the version is automatically detected by running the Jupyter Notebook version command. The version of Jupyter Notebook being used.
The Jupyter comman to run when starting a Notebook session. Running against multiple different Jupyter versions simultaneously in different Launcher clusters is not supported - they must all be running the same version, or proxying issues will occur.Īrguments to be passed to the Jupyter Lab command.
If set to auto, the version is automatically detected by running the Jupyter Lab version command. The Jupyter command to run when starting a Lab session. The following table lists the various configuration options that are available to be specified in the nf configuration file:Įnables launching of JupyterLab sessions.Įnabled launching of Jupyter Notebook sessions. Note that this file is not automatically created by RStudio, and must be created before being configured, and the Jupyter feature is disabled by default. Configuration of the Jupyter feature is handled via the config file /etc/rstudio/nf.
0 kommentar(er)
