Hi Charles, Thanks for the response.
However, I don't quite understand your set-up. I assume that via JupyterLab the port issue can be dealt with, but what happens in an interactive job? Don't users still have to run something like rserver --server-daemonize=0 --www-port=8787 as described in the current EasyBuild EC? Your EC doesn't contains such a line. Cheers, Loris Charles Coulombe <charles.coulo...@calculquebec.ca> writes: > Hi Loris, > > At the Alliance, we use this configuration file for RStudio-Server: > https://github.com/ComputeCanada/easybuild-easyconfigs/blob/computecanada-main/easybuild/easyconfigs/r/RStudio-Server/RStudio-Server-4.2-gcccoreflexiblas-2020a.eb > > > Each user loads the module in a slurm job and can start it from a JupyterLab > instance for example, or from an interactive job. > > Cheers, > > On Thu, Nov 2, 2023 at 11:56 AM Loris Bennett <loris.benn...@fu-berlin.de> > wrote: > > Hi, > > This is not really an EasyBuild question, but as there is no current > RStudio EC but just an RStudio Server EC, I thought I would ask here: > > How is RStudio Server supposed to be used? Does each user start his or > her own server? If so, how are potential port conflicts dealt with? If > not, is it just supposed be started by an admin and run on the head > node? > > Cheers, > > Loris > > -- > Dr. Loris Bennett (Herr/Mr) > ZEDAT, Freie Universität Berlin > -- Dr. Loris Bennett (Herr/Mr) ZEDAT, Freie Universität Berlin
