Only required if not using unix domain sockets. If using the default launcher configuration that ships with Workbench, this should be localhost (assuming you run the launcher side-by-side with Posit Workbench). TCP host/IP of the launcher host, or unix domain socket path (must match /etc/rstudio/nf configuration value). This must be enabled to use the Job Launcher. The following table lists the various configuration options that are available to be specified in the nf configuration file: Server optionsĮnables launching of rsession processes via the Job Launcher. The Posit Workbench process rserver must be configured to communicate with the Job Launcher in order to enable session launching. This makes the server user a Job Launcher admin, which is necessary to properly launch sessions on behalf of other users. The Launcher configuration parameter admin-group will by default be configured to use the group value of the Posit Workbench server user, specified in the server-user configuration parameter in nf (which defaults to rstudio-server). See the Launcher Considerations section of the Load Balancing chapter for more information. Additionally, if you wish to enable load balancing for your Posit Workbench installation there will be some extra configuration considerations. If you wish to enable another Launcher Plugin to integrate with a container orchestration system (e.g., Kubernetes) or a batch processing system (e.g., Slurm), configuration changes will be necessary. No additional configuration is necessary to enable the use of Launcher Sessions or Workbench Jobs with the Local Plugin. By default, a fresh installation of Posit Workbench comes with the Job Launcher and the Local Plugin enabled.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |