@@ -65,8 +65,34 @@ For example, the ``nbgrader_config.py`` that the notebook knows about could be p
65
65
66
66
Then you would additionally have a config file at ``/path/to/course/directory/nbgrader_config.py ``.
67
67
68
+ Use Case 3: using config from a specific sub directory
69
+ ------------------------------------------------------
68
70
69
- Use Case 3: nbgrader and JupyterHub
71
+ .. warning ::
72
+
73
+ This option should not be used with a JupyterHub installation, as it modifies
74
+ certain objects in the running instance, and can probably prevent other users
75
+ from using *formgrader * correctly. If you have a JupyterHub installation,
76
+ you should use the settings described in the following section.
77
+
78
+ You may need to use a dedicated configuration file for each course without configuring
79
+ JupyterHub for all courses. In this case, the config file used will be the one from the
80
+ current directory in the filebrowser panel, instead of the one from the directory where
81
+ the jupyter server started.
82
+
83
+ This option is not enabled by default. It can be enabled by using the settings panel:
84
+ *Nbgrader -> Formgrader * and check *Allow local nbgrader config file *.
85
+
86
+ A new item is displayed in the *nbgrader * menu (or in the command palette), to open
87
+ formgrader from the local director: *Formgrader (local) *.
88
+
89
+ .. warning ::
90
+
91
+ If paths are used in the configuration file, note that the root of the relative
92
+ paths will always be the directory where the jupyter server was started, and not
93
+ the directory containing the ``nbgrader_config.py `` file.
94
+
95
+ Use Case 4: nbgrader and JupyterHub
70
96
-----------------------------------
71
97
72
98
.. seealso ::
0 commit comments