Beyond the default configuration settings, you can configure a rich array of options to suit your workflow. Here are areas that are commonly configured when using Jupyter Notebook:
Let’s look at highlights of each area.
Jupyter’s Common Configuration system#
Jupyter applications, from the Notebook to JupyterHub to nbgrader, share a common configuration system. The process for creating a configuration file and editing settings is similar for all the Jupyter applications.
Disabling Custom CSS#
Custom CSS is loaded by default as was done with Jupyter Notebook 6. In the jupyter configuration directory, the
/.jupyter/custom/custom.css file will be loaded unless the the application is initialized with the
custom_css flag with the argument set to
False as in
The Jupyter Server runs the language kernel and communicates with the front-end Notebook client (i.e. the familiar notebook interface).
Configuring the Jupyter Server
To create a
jupyter_server_config.pyfile in the
.jupyterdirectory, with all the defaults commented out, use the following command:$ jupyter server --generate-config
Related: Configuring a language kernel to run in the Jupyter Server enables your server to run other languages, like R or Julia.
Jupyter Notebook 7 is now based on Jupyter Server. This may break some previous
notebook imports you may have been using, such as
Check out the migration guide to learn more on how to update these server imports.
The Notebook frontend can be extending with JupyterLab extensions.
See the Frontend Extension Guide for more information.
Security in Jupyter notebooks: Since security policies vary from organization to organization, we encourage you to consult with your security team on settings that would be best for your use cases. Our documentation offers some responsible security practices, and we recommend becoming familiar with the practices.