Contents root_dir

[davidbrochart]

Problem

Jupyverse currently serves contents relatively to the directory it was launched in. We should have a notion of root directory, which gives access to the file system in this directory and below.

Proposed Solution

Add root_dir to the contents plugin configuration.

[specter119]

Two behaviors of jupyverse are not performed as the previous.

• the os.getcwd() always returns the working folder where jupyverse started, previously it will be parent folder of the editing ipynb.
• sys.path contains the '.' (previously) and then some functions can be directed import from the py files located in the same folder.

Then if I want to directly import functions from py files located in the same folder of ipynb, the os.getcwd() should be changed following the file editing actively.

[davidbrochart]

Thanks for pointing that out @specter119, we should indeed have the same behavior as jupyter-server.
I'm not sure it is related to the root directory though, but maybe to how we create kernel clients.

[davidbrochart]

We should probably pass a path to launch a kernel in, as it is done in jupyter-server.
Currently we don't.

[davidbrochart]

I opened #245 for the kernel cwd issue.

[specter119]

@davidbrochart Thx