We really need to be able to offer much more fine-grained access controls, so that the (legitimate) user-help scenarios where the “let me become you” usage that we take advantage of all the time can be used, while not exposing these generic gaping holes… When JupyterLab is deployed with JupyterHub it will show additional menu items in the File menu that allow. On hosted systems, we typically think of root as a tiny set of operators who follow very strict protocols- I know root at an HPC center can do anything with my account, but I also trust that they don’t very strongly… JupyterLab on JupyterHub¶.JupyterLab works out of the box with JupyterHub 1.0+, and can even run side by side with the classic Notebook. Thanks for the great work, this extension is an excellent tool for many users with less experience at the command line!įyundamentally the problem with the admin feature is that it’s a quasi free-for-all “tons of people can be root” with minimal safeguards. But in the long run I’d prefer to have the GUI integrate with the credentials management options directly. Git Credential Manager Core for https clones.įor now I’m setting up my SSH agent in a terminal, and using the terminal for push/pulls while taking advantage of the GUI for other operations, and I can also explain that to my students.JupyterLab will eventually replace the classic Jupyter Notebook. To learn more about extensions, see the user documentation. JupyterLab is the next-generation user interface for Project Jupyter offering all the familiar building blocks of the classic Jupyter Notebook (notebook, terminal, text editor, file browser, rich outputs, etc.) in a flexible and powerful user interface. To find JupyterLab extensions, search for the npm keyword jupyterlab-extension or the GitHub topic jupyterlab-extension. JupyterLab can be extended using npm packages that use our public APIs. While doing full-on credentials management is certainly outside the scope of this extension, it may be possible to hook into: JupyterLab will eventually replace the classic Jupyter Notebook. In those cases, more advanced users can certainly set up ssh-agent in a terminal, which works (that’s what I do), but they still lose the ability to push from this GUI. While the solution of using a local manager is viable for local installations, it’s much trickier in remotely hosted Hubs, that are typically Linux instances in the cloud (or similar). The issue of easier integration with git credentials management has already been discussed at least in #299 and #348.
Is your feature request related to a problem? Please describe.
0 kommentar(er)
